e2e: implement OCI fetchConfig coverage for all certified providers

While a full airgap + provisioning test suite is very welcome, some coverage can be simply implemented at CAPIProvider level only. For example, a new test suite (or the existing capiprovider e2e suite) can be used to test that providers are installable with OCI artifacts. Acceptance Criteria: - Install all Certified providers (including the CAPI Core provider) using OCI fetchConfig - Verify that the deployments are available (no pod start error, image pull failures, etc.) - Verify that the deployments have the expected image tag - Verify that the deployments have the correct overridden image repository (registry.suse.com/*) - Ensure all deployments are covered if a provider contains multiple, for example azure-service-operator