trustauthority-cli: initial package addition

[arc9693]

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

What does the PR accomplish, why was it needed?
Intel® Trust Authority includes an Attestation Client CLI that provides a command line interface for attesting various platforms. The client CLI is built using the Go language and is available in the Intel Trust Authority Client for Go repository. The client CLI is used to collect evidence from the underlying host and request attestation tokens from Intel Trust Authority. The client CLI can also be used to verify Intel Trust Authority attestation tokens. This PR adds the trustauthority-cli package to the Mariner repository. This is in support to enable AzLinux guest OS CVM.

https://docs.trustauthority.intel.com/main/articles/integrate-go-tdx-cli.html

Change Log

• Change
• Change
• Change

Does this affect the toolchain?

YES

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=695100&view=results

[trungams]

Spec LGTM. Do we need this package in PMC (over building from source) or is it mainly for convenience?

[arc9693]

Spec LGTM. Do we need this package in PMC (over building from source) or is it mainly for convenience?

This is mainly for convenience.

[0xba1a]

Spec LGTM. Do we need this package in PMC (over building from source) or is it mainly for convenience?

This is mainly for convenience.

Can't this be added to Specs-Extended?

[0xba1a]

Converted to draft due to inactivity