Add update-ssh-keys 0.3.0 to core repo in azure linux

[AkarshHCL]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Adding a new package to azurelinux .

Flatcar / Gentoo vs Azure Linux / RPM – build & packaging comparison

Aspect	Flatcar / Gentoo	Azure Linux / RPM
Cargo integration	inherit cargo	BuildRequires: cargo
Cargo invocation	Via Gentoo cargo.eclass	Explicit cargo build …
Build implementation	Hidden inside cargo.eclass	Declared in %build section
Dependency specification	CRATES list + SRC_URI	Vendored crates tarball
Cargo registry	Portage-managed local registry	.cargo/config with vendor/
Offline build	Yes (pre-fetched crates)	Yes (--offline)
Target architecture	Implicit via CHOST	Explicit --target=%{rust_def_target}

Reference-https://devmanual.gentoo.org/eclass-reference/cargo.eclass/index.html

Change Log

-LICENSES-AND-NOTICES/SPECS/data/licenses.json
-LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md
-SPECS/update-ssh-keys/update-ssh-keys.signatures.json
-SPECS/update-ssh-keys/update-ssh-keys.spec
-cgmanifest.json

Does this affect the toolchain?

NO

Test Methodology

Screenshot of successful build-

[mayankfz]

Would request to push the vendor tarballs, then we can publish and merge the changes

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1082278&view=results

[sandeepkarambelkar]

Buddy Build with dependent packages - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1082318&view=results

[sandeepkarambelkar]

Changes LGTM
We need to merge coreos-init and cloud-init first before merging this.
The buddy build is performed with PR from all the other package changes.

[sandeepkarambelkar]

Buddy Build after latest merge - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1082687&view=results