Add changelog for v1.16.1

[willie-yao]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Adds a changelog file for the impending CAPZ v1.16.1 patch release.

Which issue(s) this PR fixes:

N/A

Special notes for your reviewer:

• cherry-pick candidate

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

NONE

[willie-yao]

/assign @jackfrancis

[willie-yao]

/assign @nojnhuh

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.25%. Comparing base (25d5985) to head (153d868).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5122   +/-   ##
=======================================
  Coverage   51.25%   51.25%           
=======================================
  Files         273      273           
  Lines       24651    24651           
=======================================
+ Hits        12634    12636    +2     
+ Misses      11231    11229    -2     
  Partials      786      786           

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

[willie-yao]

Gonna open a separate PR to fix hard-coded links to capz.sigs.k8s.io instead of using local files https://github.com/kubernetes-sigs/cluster-api-provider-azure/actions/runs/10797918901/job/29950239288?pr=5122

[nojnhuh]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 87d2a214490bdf6f523e396ec537d1e2fc6023ec

[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

[willie-yao]

/hold
@nojnhuh Will need to fix the links in the docs. I'll just do it in this PR and then fix it upstream if that's okay!

[nojnhuh]

@willie-yao Do we also need the link updates on the release branch?

[willie-yao]

@willie-yao Do we also need the link updates on the release branch?

Yes I think so. I'll create a separate PR to main with the link fix commit and then backport it to 1.16

[willie-yao]

Opened #5123 PTAL @nojnhuh

[willie-yao]

/hold cancel

[nojnhuh]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 49b42dc2f6c9c089c5bb62fb07da1ce63122b241