Add profiler-patched agent snapshot to S3 publish

[jbachorik]

What Does This Do

Adds a new GitLab CI job publish-profiler-patched-agent-to-s3 in the publish stage. On every pipeline it:

1. Shallow-clones DataDog/java-profiler to get utils/patch-dd-java-agent.sh
2. Downloads the latest ddprof.jar from the java-profiler GitHub releases
3. Patches the stock dd-java-agent.jar with the latest profiler native libraries
4. Uploads dd-java-agent-profiler.jar to s3://dd-trace-java-builds at both the branch-name and pipeline-ID paths

Motivation

Enables forward-testing of new profiler releases against the latest agent snapshot without a full rebuild.

Additional Notes

• No auth required — DataDog/java-profiler is public and assets are downloaded via plain HTTPS
• Uses the same amazon/aws-cli:2.4.29 image as the sibling publish-artifacts-to-s3 job
• Fails fast if the release asset is missing or the patch script exits non-zero

tag: no release note
tag: ai generated

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]