Reconsider version scheme for tags

[jwortmann]

LSP currently uses a 4070- prefix for the Git tags.

According to https://www.sublimetext.com/blog/articles/sublime-text-4200 the Python 3.8 plugin host will be replaced with Python 3.13 in future versions of Sublime Text. If we want to use Python 3.13 syntax, we need to update the version restrictions for LSP in https://github.com/sublimelsp/repository.

I would suggest that as soon as a stable build with Py 3.13 comes out - say build 4220 - we create a new LSP release and two tags, one with the 4070- prefix and another one with just a v prefix (like v2.9.0), and update the channel data accordingly:

			"releases": [
				{
					"sublime_text": "3154 - 3999",
					"tags": "3154-"
				},
				{
					"sublime_text": "4132 - 4200",
					"tags": "4070-"
				},
				{
					"sublime_text": ">=4201",
					"tags": true
				}
			],

From then on we continue to use the regular semantic versioning tags without 4070- prefix. I assume that this prefix was intended to be updated whenever required by usage of a new API functionality, but this wasn't done a single time in the last five years or so, and the version prefix doesn't even match the actual version requirement, because apparently it was missed to track the used API functions and update the prefix accordingly. Also this 4070- prefix looks somewhat ugly.

When in a few years ST updates the Python version again, or adds some new API functionality which prompts LSP to drop backwards compatibility, we can just create another tag with the corresponding version prefix (4201-), add that to the channel data, and keep using the v prefix for the regular new releases.