🌱 refactor: drop obsolete pending e2e tests

[Arpit529Srivastava]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:

this pr removes two long-standing pdescribe (pending) e2e tests: the dedicated hosts cluster test, which was removed due to the high cost of dedicated hosts and the absence of a required template and the vpc peering tesst, which was removed because it covered a complex setup involving vpc peering, internal elbs and external security groups that is better handled by simpler and more maintainable tests (eg, in unmanaged_functional_clusterclass_test.go). it also cleans up unused help_

addresses #5176

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

NONE

[k8s-ci-robot]

[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 assign dlipovetsky for approval. For more information see the Code Review Process.

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

Details

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Arpit529Srivastava / name: Arpit Srivastava (9cffc5c)

[k8s-ci-robot]

Welcome @Arpit529Srivastava!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Arpit529Srivastava. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[Arpit529Srivastava]

/cc @richardcase PTAL.
thanks

[AndiDog]

/lgtm
/ok-to-test

I guess @richardcase might know something about the cost topic?

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: 40caddafccb045ddc0aaf430534492ccaa83f7d8