feat(source/ambassador): update Host CRD to v3alpha1

[danopia]

The datawire/ambassador repository has been renamed to emissary-ingress/emissary. The latest CRD version has been v3alpha1 for a long time, but as of release 3.10 the installation guide no longer installs v2 CRDs, which breaks the external-dns ambassador source.

What does it do ?

Updates the ambassador dependency (following a repository rename) and switches from the v2 CRD to the v3alpha1 CRD.

I am successfully running an image from this branch on a fresh cluster. The upstream image goes into CrashLoopBackOff.

Motivation

external-dns doesn't work with a fresh emissary-ingress installed using the 3.10 QUICKSTART.md guide.

See also:

• Failed to use --source=ambassador-host with 3.X emissary branch versions #5724

More

• Yes, this PR title follows Conventional Commits
• Yes, I added unit tests
• Yes, I updated end user documentation accordingly

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

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

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

[k8s-ci-robot]

Hi @danopia. 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.