Implement sanity checks in `since`, `readme`, and `versions` commands

[felixarntz]

Over the past few months, several enhancements have been implemented to make the since, readme, and versions commands more intelligent so that they can automatically determine the relevant versions rather than requiring them as arguments, making these commands easier to use.

A potential downside of the way this currently works is that it can lead to errors, because the person running the command is no longer explicitly required to think about what the versions they want to prepare the code for actually are. For instance, you could run the since command anytime, leading to @since annotations in the new code being for a version that has already been released.

This issue proposes adding sanity checks to the version detection done by those command scripts. It should check to ensure that the version detected locally is not already available in WordPress.org, effectively leading to a more explicit requirement that the commands must only be used once the version has been bumped to the next version in plugin main file and readme.

More concretely, I'm proposing something along the lines of:

1. After parsing the version from plugin main file / readme, check wordpress.org for that plugin.
2. If this version is already released, skip running the process for said plugin, and emit a log that indicates that.
3. If the version is not already released (including if the entire plugin is new), run the process for said plugin as usual.

This would give us peace of mind that we don't accidentally provide incorrect since annotations or create incorrect changelogs.

[westonruter]

This sounds great. I believe it essentially implements the todo I added to the releasing standalone plugins handbook page:

Ensure the plugin’s version number in the GitHub repository codebase is higher than the currently published version in the wordpress.org plugin directory (for an update), or there is no published version in the wordpress.org plugin directory yet (for a first-time release). (TODO: This should be automated.)

[thelovekesh]

Something similar exists for plugin release workflow:

performance/.github/workflows/deploy-plugins.yml

Lines 83 to 102 in 35dfc9c

	- name: Check if deployment is needed
	id: check-deployment
	run: |
	PLUGIN_VERSION_WPORG=$(curl -sSL https://api.wordpress.org/plugins/info/1.0/${{ matrix.plugin }}.json --retry 3 --retry-delay 5 --retry-all-errors --fail | jq -r '.version')
	echo "::debug::The ${{ matrix.plugin }} plugin is currently at version $PLUGIN_VERSION_WPORG on WordPress.org."
	# Bail if the plugin version is not found.
	if [ -z "$PLUGIN_VERSION_WPORG" ]; then
	echo "::error::Could not retrieve ${{ matrix.plugin }} information from WordPress.org. The plugin may not exist or the API may be down."
	exit 1
	fi
	# Bail if the plugin is already up to date.
	if [ "$PLUGIN_VERSION_WPORG" = "$PLUGIN_VERSION" ]; then
	echo "::notice::The ${{ matrix.plugin }} plugin is already up to date on WordPress.org. Halting deployment."
	exit 0
	fi
	echo "deploy=true" >> $GITHUB_OUTPUT

Maybe we need to extract this into a different script and use it across all commands/workflows.