Stop using s3 for packaging signing key

What does this MR do?

Stop using s3 for packaging signing key

- Stop pulling the package signing key from s3. This removes the final
  dependency requirement for awscli in the container build images.

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8393

Related https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8398

Related https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/issues/78

Related https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/issues/77

Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

Related issues

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8393+s

Related Add Debian 12 Raspberry Pi Package Build Jobs (#8398 - closed) • Robert Marshall

Related Remove awscli from build container images (gitlab-omnibus-builder#78 - closed) • Robert Marshall • 16.9

Related Add Debian 12 Raspberry Pi container build images (gitlab-omnibus-builder#77 - closed) • Robert Marshall • 16.9

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• Latest Merge Result pipeline is green.
• When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

• The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
• If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
• If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
• If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes.
• Documentation created/updated.
• Tests added.
• Integration tests added to GitLab QA.
• Equivalent MR/issue for the GitLab Chart opened.
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.