Set Aws credentials in cert manager package pod for e2e test

[rajeshvenkata]

Issue #, if available:
#9177

Description of changes:
In testing cert manger, we use access key and Id (see here) to test cert manager. ClusterIssuer does not have support for session token. One workaround is to use Ambient credentials approach where environment variables like AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN are set in the cert manager pod.

In this PR, I am adding a test data (with AWS credentials - key, id, sessiontoken) for cert manager and use that to create cert manager pod and remove the current logic of using access key and id in the cluster issuer.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from rajeshvenkata. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.47%. Comparing base (a87378e) to head (5985f7d).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9455   +/-   ##
=======================================
  Coverage   69.47%   69.47%           
=======================================
  Files         672      672           
  Lines       49381    49381           
=======================================
  Hits        34307    34307           
  Misses      13288    13288           
  Partials     1786     1786           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rajeshvenkata]

/retest-required

[rajeshvenkata]

/retest-required

[eks-distro-bot]

@rajeshvenkata: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
eks-anywhere-e2e-presubmit	5985f7d	link	true	/test eks-anywhere-e2e-presubmit

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.