test: add test-pods namespace creation for AWS test-infra

[andyzhangx]

What type of PR is this?
/kind failing-test

What this PR does / why we need it:
test: add test-pods namespace creation for AWS test-infra

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

none

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

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

[andyzhangx]

/retest

[coveralls]

Pull Request Test Coverage Report for Build 10304630983

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 78.831%

---

Totals
Change from base Build 10294581952:	0.0%
Covered Lines:	890
Relevant Lines:	1129

---

💛 - Coveralls

[andyzhangx]

/retest

[andyzhangx]

/retest

[andyzhangx]

/test pull-csi-driver-nfs-external-e2e

[k8s-ci-robot]

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

Test name	Commit	Details	Required	Rerun command
pull-csi-driver-nfs-external-e2e	5036b40	link	true	/test pull-csi-driver-nfs-external-e2e
pull-csi-driver-nfs-e2e-capz	5036b40	link	false	/test pull-csi-driver-nfs-e2e-capz

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.