Eliya distribution: populate checksum, signature_uri, and download_site_uri fields

[fahimfarookme]

Follow-up from #156.

1. A few metadata fields could not be populated yet
The Eliya connector is returning all 8 packages correctly. Few metadata fields could not be populated yet, so tracking them separately here.

Endpoint
On every Eliya package returned from /v3.0/packages?distribution=eliya and from the per-id /ids/<id> endpoint

Metadata fields and suggested mapping

Field	Suggested value
download_site_uri	https://asymm.systems/product/eliya
checksum	the per-file SHA-256 below
checksum_type	"sha256"
checksum_uri	https://github.com/asymmsystems/eliya-jdk/releases/download/eliya-jdk-25.0.3/SHA256SUMS.txt
signature_uri	https://github.com/asymmsystems/eliya-jdk/releases/download/eliya-jdk-25.0.3/SHA256SUMS.txt.asc

The data is on the release. SHA256SUMS.txt carries per-file SHA-256, and SHA256SUMS.txt.asc carries the aggregate detached GPG signature. Per-file values for 25.0.3:

7afe774c0c837fd06b9908a65278dc4cc71eb0ec6b0d794dd7b0687da79bbec4  eliya-jdk-25.0.3-linux-aarch64.tar.gz
5ede53be159ebdb4644850df0465116b90664c4b929e9b8d7cc3a45cfce3d164  eliya-jdk-25.0.3-linux-x64.tar.gz
e90f38a963d4bb33ec7bcd6ebeea2fc3122a6e10437ae6ecba1307525f78fd9c  eliya-jre-25.0.3-linux-aarch64.tar.gz
d93c6fb4937b15b1e1de3240d5a65b856027270f92bc94404fd83298a357e45e  eliya-jre-25.0.3-linux-x64.tar.gz
23975f1ce8af09faf9b5e2b562307c6cc4af9ea9075edea380e232b7c75d10c3  eliya-jdk_25.0.3_amd64.deb
2821bec966e47cdd7e89c54cb24fb6322d5407d4f0da028ffe5862edb100d7a9  eliya-jdk_25.0.3_arm64.deb
75670fffa60ade8e6fd6196b544eacd4d1c5df2fbcecfafbc2fc5b1e5b403e6e  eliya-jdk-25.0.3.aarch64.rpm
2ec91439a56c58455cbee628e5a5910ae5081c136a500786090448abc3e18771  eliya-jdk-25.0.3.x86_64.rpm

2. Minor: intra-Eliya arch-token inconsistency.
Eliya's own packages report amd64 on the .deb and x64 on the .rpm / .tar.gz for the same x86_64 CPU. For comparison, Liberica reports amd64 across all three formats on Linux. Could the Eliya connector emit one token per CPU regardless of format? No rush; lowest priority

[HanSolo]

Added all modifications and deployed it to testing, at the moment I'm deploying it to staging and after to production, let's hope it will work as expected :)

[HanSolo]

Ok, the deployment to production is done, it will take some time until the update will appear because it will first remove the existing packages and then scan for the new ones which happens once a day. So I expect the new packages to show up at least on Sunday.