Run/fix DynamicPV tests in CI & remove redundant tests

[wongma7]

/kind bug

What happened?
Old TODO: https://github.com/kubernetes-sigs/aws-fsx-csi-driver/blob/master/tests/e2e/conformance_test.go#L136

IIRC we are skipping the DynamicPV tests because of an issue in the framework where it would only wait 5 minutes for a volume to be created but that issue has been solved for a long time now.

Running them will allow us to refactor/get rid of some of the custom tests, for example 2/3 of the ones here https://github.com/kubernetes-sigs/aws-fsx-csi-driver/blob/master/tests/e2e/dynamic_provisioning_test.go#L55, and maybe reduce some of the code duplicated from upstream like driver struct https://github.com/kubernetes-sigs/aws-fsx-csi-driver/blob/master/tests/e2e/driver/driver.go#L23

(obviously this is blocked by CI being 100% broken at the moment)

What you expected to happen?

How to reproduce it (as minimally and precisely as possible)?

Anything else we need to know?:

Environment

• Kubernetes version (use kubectl version):
• Driver version:

[wongma7]

since the script in #172 is creating a 1.20 cluster, need to fix #183

[wongma7]

one more consideration is test time, they are slow since all tests involve creating an fsx volume (pre-provisioned the test calls aws api, dynamic the driver calls was api). Don't need to run the dynamic+pre-provisioned variation of every test. Maybe run all dynamic cases and run just 1 pre-provisioned case

[wongma7]

Also , need to debug why a specific subPath test fails: https://github.com/kubernetes-sigs/aws-fsx-csi-driver/blob/master/Makefile#L51

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[wongma7]

/lifecycle frozen

now that CI is fixed, should try to untangle dynamic PV tests