Use ipv6 template for ipv6 conformance instead of default template

[nojnhuh]

What type of PR is this?
/kind bug

What this PR does / why we need it:

The ipv6 conformance job has been effectively equivalent to the regular conformance job because the job is configured to set IP_FAMILY to ipv6 but the test is expecting IPv6 to switch the template and e2e config. Other uses of IP_FAMILY that I can find all use ipv6, so this PR updates the test to look for that value.

https://github.com/kubernetes/test-infra/blob/6ff24f80fad13b8a2f8b3a19a00e717c46964fee/config/jobs/kubernetes-sigs/cluster-api-provider-azure/cluster-api-provider-azure-presubmits-main.yaml#L395-L396

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

TODOs:

• squashed commits
• includes documentation
• adds unit tests
• cherry-pick candidate

Release note:

NONE

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.82%. Comparing base (5ae25f7) to head (2cccc8d).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5755   +/-   ##
=======================================
  Coverage   52.81%   52.82%           
=======================================
  Files         279      279           
  Lines       29629    29629           
=======================================
+ Hits        15650    15652    +2     
+ Misses      13162    13160    -2     
  Partials      817      817           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mboersma]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: bb4b030af25b3019017bca5322399a771a00cca9

[mboersma]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mboersma

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

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

[mboersma]

/cherry-pick release-1.20

[mboersma]

/cherry-pick release-1.19

[k8s-infra-cherrypick-robot]

@mboersma: new pull request created: #5760

In response to this:

/cherry-pick release-1.20

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.

[k8s-infra-cherrypick-robot]

@mboersma: #5755 failed to apply on top of branch "release-1.19":

Applying: Use ipv6 template for ipv6 conformance instead of default template
Using index info to reconstruct a base tree...
M	docs/book/src/developers/development.md
M	test/e2e/config/azure-dev.yaml
M	test/e2e/conformance_test.go
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/conformance_test.go
CONFLICT (content): Merge conflict in test/e2e/conformance_test.go
Auto-merging test/e2e/config/azure-dev.yaml
CONFLICT (content): Merge conflict in test/e2e/config/azure-dev.yaml
Auto-merging docs/book/src/developers/development.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Use ipv6 template for ipv6 conformance instead of default template

In response to this:

/cherry-pick release-1.19

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.