[v9] End beta period and update release tooling for select products

[ncooke3]

Fixes #9367

[google-oss-bot]

Coverage Report ¹

Affected Products

• FirebaseFirestore-iOS-FirebaseFirestore.framework

  Filename	Base (415e9ea)	Merge (69da4ce)	Diff
  local_serializer.cc	89.42%	88.58%	-0.84%
  ordered_code.cc	93.41%	94.15%	+0.73%

Test Logs

• Base (415e9ea): https://github.com/firebase/firebase-ios-sdk/actions/runs/2111605187
• Merge (69da4ce): https://github.com/firebase/firebase-ios-sdk/actions/runs/2111628189

1. https://storage.googleapis.com/firebase-sdk-metric-reports/gwkpyU1Vq8.html

[paulb777]

LGTM on CI run as good as master

[morganchen12]

LGTM, but please label breaking changes in the release notes (and, if applicable, actions users should take to resolve breakages).

[paulb777]

Good point, we should document the necessary changes to the Podfile's and how to update an existing SPM project using one of the beta targets.

[ncooke3]

Good point, we should document the necessary changes to the Podfile's and how to update an existing SPM project using one of the beta targets.

Thanks @paulb777 for mentioning SPM. So, for CocoaPods users, moving products out of beta will not affect them, correct?
But for SPM users, it will if the name of the library changed? Because they will try to update a product that no longer exists?

[paulb777]

It does affect existing CocoaPods users because they need to remove the explicit beta specification from their Podfile. See https://stackoverflow.com/a/64671117/556617 just like we'll need to do in our quickstarts.

Yes, SPM users will be specifying a no longer existing product.

[ncooke3]

I've updated the CHANGELOGs to reflect that moving out of beta is a breaking change (see above discussion).

There were two zip / quickstart failures that I believe are being addressed by #9607.

[ncooke3]

cc: @weixifan