🐛: fix unknown provider errors when using fetchConfigs

[w21froster]

What this PR does / why we need it:
When using fetchConfig in the provider spec for multiple providers, the operator does not properly pass information about other "custom" providers to the clusterctl configuration. Currently, the operator passes repository information about the current provider only, and the default list from clusterctl. This causes clusterctl to fail it's lagging provider check, which is intended to keep providers within a valid version skew to avoid a broken cluster, and prevents upgrading providers when using fetchConfig in multiple places.

This PR adds information about other providers that are using fetchConfig to the MemoryReader, so that clusterctl can properly pass this check.

Which issue(s) this PR fixes:
Fixes #570

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: w21froster / name: Will Foster (53b604a, de29d47, 02da990, b98394f, 2dc4296, cc7397b)

[k8s-ci-robot]

Welcome @w21froster!

It looks like this is your first PR to kubernetes-sigs/cluster-api-operator 🎉. 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-operator 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 @w21froster. 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.

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.

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-operator ready!

Name	Link
🔨 Latest commit	b98394f
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-operator/deploys/67c609fe61b5460008e7e5cb
😎 Deploy Preview	https://deploy-preview-730--kubernetes-sigs-cluster-api-operator.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dmvolod]

/ok-to-test

[w21froster]

/retest

[furkatgofurov7]

/test?

[k8s-ci-robot]

@furkatgofurov7: The following commands are available to trigger required jobs:

/test pull-cluster-api-operator-build-main

/test pull-cluster-api-operator-e2e-main

/test pull-cluster-api-operator-make-main

/test pull-cluster-api-operator-test-main

/test pull-cluster-api-operator-verify-main

The following commands are available to trigger optional jobs:

/test pull-cluster-api-operator-apidiff-main

Use /test all to run all jobs.

In response to this:

/test?

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.

[furkatgofurov7]

/test pull-cluster-api-operator-e2e-main

[w21froster]

This PR is ready for a final review whenever you folks have a chance, let me know if there is anything else I can fix / update here. I appreciate your help! 🙏

[furkatgofurov7]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: furkatgofurov7

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 [furkatgofurov7]

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

[w21froster]

Hey folks, sorry for the bump, anything else needed from me on this PR to get the LGTM? I went ahead and rebased off main. Thank you 🙇

[furkatgofurov7]

This is a huge patch, however, it is due to manifests included and changes are inside the test folder anyways, so I am merging it.

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 68418b1740f8415fc9c29d109ac3f6358b3c423f

[furkatgofurov7]

Thanks @w21froster working on the fix, appreciated 🥇