[main](backport #43040) [8.18](backport #43029) [main](backport #42980) docs: Prepare Changelog for 8.17.3

[mergify]

Prepare Changelog for 8.17.3.

Merge once the BC that will be published is decided.

---

This is an automatic backport of pull request #42980 done by Mergify.

---

This is an automatic backport of pull request #43029 done by Mergify.

---

This is an automatic backport of pull request #43040 done by Mergify.

[mergify]

Cherry-pick of 37eac6b has failed:

On branch mergify/bp/main/pr-43040
Your branch is up to date with 'origin/main'.

You are currently cherry-picking commit 37eac6b68.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   CHANGELOG.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/main/pr-43040 upstream/mergify/bp/main/pr-43040
git merge upstream/main
git push upstream mergify/bp/main/pr-43040

[botelastic]

Hi!
We just realized that we haven't looked into this PR in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

[botelastic]

Hi!
This PR has been stale for a while and we're going to close it as part of our cleanup procedure.
We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team.
Feel free to re-open this PR if you think it should stay open and is worth rebasing.
Thank you for your contribution!