[Tooling] Use Release Version from ReleasesV2 in Code Freeze

[iangmaia]

Closes AINFRA-1376: WCiOS: Validate that release version sent by ReleasesV2 matches the project

Description

This PR updates the code freeze process to use the release version provided by ReleasesV2 as the source of truth.

The code freeze Buildkite pipeline now passes the RELEASE_VERSION environment variable to the code_freeze Fastlane lane.
If there's a mismatch between the passed version and the project calculated version, a warning is displayed to help identify configuration discrepancies, but the ReleasesV2 version is always used.

Testing

The code freeze lane has several side effects like potentially changing the version in the main branch, creating a release branch, updating release notes, etc, making it hard to easily test it. We can run a couple of tests locally commenting out parts of the lane, but they'll only test a minor part of the lane.
The changes will then be fully tested in the next release cycle during code freeze.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce iOS Prototype by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce iOS Prototype
	Build Number	pr16232-0425644
	Version	23.4
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	0425644
	Installation URL	41osund78mmi8

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[AliSoftware]

I have the same feedback as on https://github.com/bloom/DayOne-Android/pull/6612#pullrequestreview-3319847686, and given there's a batch of those PRs across repos, so let's focus the code review feedback on that single DOAndroid PR to avoid spreading the discussions, and merge the various repo's PRs all at once once the feedback have been addressed across all of them :)