Merge release/2.2 into master

[mongodb-drivers-pr-bot]

Merge new changes from release/2.2 into master.

Commits

• Merge pull request Merge release/2.1 into release/2.2 #2041 from mongodb/merge-release/2.1-into-release/2.2-1746485012973: f42e076
• Merge branch 'release/2.2' into merge-release/2.1-into-release/2.2-1746485012973: 9406f3f
• Merge pull request Merge release/2.0 into release/2.1 #2040 from mongodb/merge-release/2.0-into-release/2.1-1746482425951: 67dc47c
• Merge branch 'release/2.1' into merge-release/2.0-into-release/2.1-1746482425951: e308012
• DEVPROD-17319 Update perf.send command to new results end point (DEVPROD-17319 Update perf.send command to new results end point #2032): 6619fd8

Resolving conflicts

To resolve any conflicts, check out the temporary branch and run the following command:

git merge master

Ignoring changes

To ignore from the remote branch, first reset the temporary branch to master and manually merge using the `ours` merge strategy:

git reset --hard master
git merge --strategy=ours release/2.2

Then, push the temporary branch to upate the pull request.

[mongodb-drivers-pr-bot]

API Change Report

No changes found!

[prestonvasquez]

We don't traditionally update master with patch version.

[evergreen-ci-prod]

There is an existing patch(es) for this commit SHA:

• Evergreen patch with PR
• Evergreen patch with PR

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.

[alcaeus]

Manually excluded the bump commit to ensure release/2.2 is fully merged into master. I'll create a separate PR to mark the bump commit as merged without applying changes.