feat(auth): move encryption to LanguageClientAuth and encrypt profile data

[liramon1]

Problem

Our current IAM auth setup assumes profile data is transmitted in plaintext. This is not secure enough given that we are transmitting IAM credentials inside of the profile data.

Solution

• Add encryption and decryption to profile endpoints
• Move encryption to LanguageClientAuth for greater reusability

---

• 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.

[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.

[Analistarjx]

Problem

Our current IAM auth setup assumes profile data is transmitted in plaintext. This is not secure enough given that we are transmitting IAM credentials inside of the profile data.

Solution

• Add encryption and decryption to profile endpoints

• Move encryption to LanguageClientAuth for greater reusability

• 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.