Split llm_runner runtime release lines

[yaroslavyaroslav]

What changed

• freeze Python 3.8/3.13 llm_runner templates at PyPI 0.2.14 for Sublime Text 4050–4204
• keep a separate floating Python 3.14 line for Sublime Text 4205+
• correct Linux arm64 templates to the actually published musllinux artifacts
• mention Python 3.14 in the channel usage documentation

Why

Package Control dependencies contain library names, not version constraints. Without separate release templates, an older Sublime/plugin line can be affected by future library publication. The fixed PyPI base and non-overlapping Sublime/Python selectors make the compatibility boundary explicit.

Impact

Old hosts resolve 0.2.14 cp38/cp313 wheels only. New hosts resolve cp314 wheels only; the currently published bridge is 0.2.13 and the next line will be 0.3.x.

Validation

• parsed repository.json with python3 -m json.tool
• ran four boundary tests using Package Control's current is_compatible_version() and version_match_prefix() implementations
• ran Package Control's own PyPiClient against live PyPI metadata: all 12 legacy templates resolve 0.2.14 and all six Python 3.14 templates resolve the current cp314 bridge

[deathaxe]

Only compatible releases are picked for each python version. If new versions of a library require py314+, latest available one will continue to be shipped for 38 and 313.

There should in general not be any requirement for version pinning, nor restricting "sublime_text" versions. The later might even be redundant with python_versions specifier.