[release-1.15] Bump CAPI to v1.7.2

[mboersma]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Manual cherry-pick of #4855.

Updates CAPI to v1.7.2.

Which issue(s) this PR fixes:

N/A, but see #4767 for prior art.

Special notes for your reviewer:

• cherry-pick candidate

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

Bump CAPI to v1.7.2

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.01%. Comparing base (100bf88) to head (898a8e3).
Report is 1 commits behind head on release-1.15.

Additional details and impacted files

@@              Coverage Diff              @@
##           release-1.15    #4858   +/-   ##
=============================================
  Coverage         62.01%   62.01%           
=============================================
  Files               201      201           
  Lines             16861    16861           
=============================================
  Hits              10456    10456           
  Misses             5622     5622           
  Partials            783      783           

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

[mboersma]

/retest

[nojnhuh]

/lgtm
/approve

/hold in case you wanted to squash, but I don't mind two commits here.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nojnhuh

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

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]

LGTM label has been added.

Git tree hash: 6bb2450ffd469751fbe58c63ccf9c8cd842f2c42

[mboersma]

/hold cancel

I don't mind two commits here

That was intentional, in case the cert-manager changes might need to be rolled back separately from the CAPI update. (Although I'm not 100% consistent about splitting commits this way, I admit.)