Merge 24.0.1 hotfix into release/24.1

[spencertransier]

This PR merges the changes from the 24.0.1 hotfix into release/24.1. Includes:

• Version bump
• Hotfix (just a Gutenberg bump): Integrate gutenberg-mobile release v1.110.1 #22437

[peril-wordpress-mobile]

	Messages
📖	This PR has the 'Releases' label: some checks will be skipped.

Generated by 🚫 dangerJS

[wpmobilebot]

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

	App Name	WordPress Alpha
	Configuration	Release-Alpha
	Build Number	pr22438-63a052d
	Version	24.1
	Bundle ID	org.wordpress.alpha
	Commit	63a052d
	App Center Build	WPiOS - One-Offs #8524

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

[wpmobilebot]

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

	App Name	Jetpack Alpha
	Configuration	Release-Alpha
	Build Number	pr22438-63a052d
	Version	24.1
	Bundle ID	com.jetpack.alpha
	Commit	63a052d
	App Center Build	jetpack-installable-builds #7547

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

[mokagio]

@spencertransier, given the PR title, I took the liberty to update the base branch from trunk to release/24.1. However, there are still merge conflicts 🤔

[spencertransier]

@mokagio I had started working on those merge conflicts when I realized that there will need to be a new version of Gutenberg that includes the hotfix as well. So I thought it made sense to wait until that is released (see p1705991079495289/1705947847.142679-slack-CC7L49W13) before finishing the merge conflicts since the first two are related to the Gutenberg version.

How would you normally handle a situation like this?