Create intermediate branches for code freeze & finalize release PRs

[oguzkocer]

This is targeting release/24.7 so that I can test it in the upcoming finalization tomorrow.

[dangermattic]

	1 Warning
:warning:	This PR is assigned to the milestone 24.7 ❄️. The due date for this milestone has already passed. Please assign it to a milestone with a later deadline or check whether the release for this milestone has already been finished.

Generated by :no_entry_sign: Danger

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[wpmobilebot]

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

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr20717-c0e5518
	Commit	c0e5518c5a13c5293063fc7ac97a6802e1a06c00
	Direct Download	wordpress-prototype-build-pr20717-c0e5518.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

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

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr20717-c0e5518
	Commit	c0e5518c5a13c5293063fc7ac97a6802e1a06c00
	Direct Download	jetpack-prototype-build-pr20717-c0e5518.apk

Note: Google Login is not supported on these builds.

[oguzkocer]

I think it's OK not to add any exceptions about these branches to buildkite-ci. The ones we currently have are branches that we trigger builds that shouldn't be canceled, such as release builds. These ones shouldn't be any different from other branches. Thanks for bringing that up anyway, because I didn't consider it before 😅