[clusterctl] Implement E2E jobs for clusterctl based UX

[fabriziopandini]

User Story

As a developer, I would like to have E2E jobs ensuring that my changes are not impacting the UX based on clusterctl

Detailed Description

#2321 is introducing a test framework for clusterctl; however, it is not yet defined:

1. What user stories based on clusterctl should be tested, e.g.:

• P0 - quick-start
• P1 - move
• P1 - upgrade
• P2 - other clusterctl features (add provider, delete provider & delete provider variants, fetch templates variants, air-gapped env, etc.)
• P2 - multitenancy variants of the above user stories

2. How to run those E2E tests

• PR blocking (only P0)
• periodic (P1 & P2)
• manual tests

This issue is aimed at defining the requirements to move on to the next step for the implementation.

Anything else you would like to add:

this work can overlap with #2636

/kind feature

[fabriziopandini]

/area clusterctl

[fabriziopandini]

/close
Now that #2884 is merged, clusterctl is being tested a part of CAPI e2e tests

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

/close
Now that #2884 is merged, clusterctl is being tested a part of CAPI e2e tests

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.