Add AWS_CONTAINER_AUTHORIZATION_TOKEN as default value for SSRF_ENV_VARIABLES

[dhinakk]

Description of changes:
This change adds AWS_CONTAINER_AUTHORIZATION_TOKEN as a default value for SSRF_ENV_VARIABLES config in addition to the already existing values AWS_TOKEN and AWS_SESSION_TOKEN.

The AWS_CONTAINER_AUTHORIZATION_TOKEN env variable contains the authorization token in ECS, EKS and even in Java Lambda's when SnapStart is enabled. Adding this env variable as another default value to SSRF_ENV_VARIABLES allows the Secrets Manager Agent to be used in the above containerized environments without developers having to manually add it.

Refer :

• https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html
• https://docs.aws.amazon.com/lambda/latest/dg/snapstart-activate.html

Verification

• cargo build succeeds and all unit tests pass.
• Manually tested by creating an Java Lambda Extension with SnapStart enabled, using the example provided, and verified that the Agent is able to retrieve secrets.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.80%. Comparing base (2081106) to head (c9174c3).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #28      +/-   ##
==========================================
- Coverage   68.89%   68.80%   -0.10%     
==========================================
  Files          14       14              
  Lines        2887     2885       -2     
  Branches       11       10       -1     
==========================================
- Hits         1989     1985       -4     
- Misses        898      900       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.