fix(sagemaker): update metrics for Jorus dashboard

[aws-ajangg]

Problem

The Jorus (SageMaker Studio) telemetry dashboard shows ~75% of events with awsAccount: not-set and awsRegion: not-set. This happens because deeplink and remote connection flows don't have active AWS credentials in the extension context, so the default telemetry injection (injectCommonMetadata) falls through to "not-set". Additionally, HyperPod deeplink events emit sagemaker_deeplinkConnect, polluting the Jorus dashboard with non-Jorus traffic.

Solution

1. Record awsAccount/awsRegion at each call site where the data is available
2. Prevent default injection from overwriting explicit values.
3. Separate HyperPod deeplink into its own metric which will remove false values tracked on Jorus dashboard

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.
• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[amazon-inspector-ohio]

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
• This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
  • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
  • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

[amazon-inspector-ohio]

✅ I finished the code review, and didn't find any security or code quality issues.