[chore] Merge release/v0.102.x into main replacement

[mx-psi]

Replacement of #10327 following step 4:

If you see merge conflicts when creating the pull request, do the following:
Create a new branch from origin:main.
Merge the release/ branch into the new branch.
Resolve the conflicts.
Create another pull request to the main branch from the new branch to replace the pull request from the release/ branch.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.58%. Comparing base (760f773) to head (2430edb).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #10328   +/-   ##
=======================================
  Coverage   92.58%   92.58%           
=======================================
  Files         387      387           
  Lines       18254    18254           
=======================================
  Hits        16900    16900           
  Misses       1008     1008           
  Partials      346      346           

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

[evan-bradley]

Not sure I understand why there are no changes, but based on the commits this looks good to me.

It does seem like it's missing the 0.102.1 release, but I think that can be done in a follow-up.

[mx-psi]

Not sure I understand why there are no changes, but based on the commits this looks good to me.

This is to get the same commit SHA on main as we have on the release/v0.102.x. The contents of all the commits are already on main, so the actual diff is nil.

It does seem like it's missing the 0.102.1 release, but I think that can be done in a follow-up.

This may actually be important I think :/ let me double check

[mx-psi]

(Please don't merge this yet even if you have permissions, I am checking the builder thing)

[mx-psi]

Need to redo the PR, sorry :(

[mx-psi]

Replaced by #10329, it was missing 7218b4c indeed