fix: propagate env var to nginx.conf in order to use IAM for Service Account properly

[cHiv0rz]

Proposed changes

Contribute to issue #414.

IAM credentials are not working, when the awscredentials.js script is trying to read the environmental variables, and those are not present. By this change, we propagate the environmental variables to nginx, and it will be possible to use the credentials provided by the SA account

Checklist

Before creating a pull request (PR), run through this checklist and mark each as complete:

• I have read the contributing guidelines.
• I have signed the F5 Contributor License Agreement (CLA).
• The PR title follows the Conventional Commits specification.
• If applicable, I have added tests that prove my fix is effective or that my feature works.
• If applicable, I have checked that any relevant tests pass after adding my changes.
• I have updated any relevant documentation (e.g. README.md).

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[cHiv0rz]

I have hereby read the F5 CLA and agree to its terms

[jarojasm95]

until this is merged I am using this script to workaround the issue during container startup

contents="env AWS_ROLE_ARN;env AWS_ROLE_SESSION_NAME;env AWS_STS_REGIONAL_ENDPOINTS;env AWS_REGION;env AWS_WEB_IDENTITY_TOKEN_FILE;";
sed -i "16i${contents}" /etc/nginx/nginx.conf;

in case it's helpful for anyone running into this

[cHiv0rz]

thanks @jarojasm95 ! I've made another workaround, creating a configmap for nginx.conf file, and mounting into /etc/nginx folder. It works as well

[erdi]

Any chance you could please have a look if this PR could be accepted, @dekobon?