refactor: rename LATEST_VERSION to LATEST_TYPESCRIPT_VERSION

[jbedard]

Fix aspect-build/rules_js#817

WDYT of changing this in 2.0+? Could add it as an alias for now...

[gregmagolan]

We could export both and update all usages and snippets to load TS_LATEST_VERSION, then its not breaking

[jbedard]

Only if we plan to remove it in 2.0. Sound good?

[gregmagolan]

We have DEFAULT_NODE_VERSION in rules_nodejs and I saw these in our bazel-examples

load("@aspect_rules_esbuild//esbuild:repositories.bzl", "esbuild_register_toolchains", LATEST_ESBUILD_VERSION = "LATEST_VERSION")

esbuild_register_toolchains(
    name = "esbuild",
    esbuild_version = LATEST_ESBUILD_VERSION,
)

load("@aspect_rules_swc//swc:repositories.bzl", "swc_register_toolchains", LATEST_SWC_VERSION = "LATEST_VERSION")

swc_register_toolchains(
    name = "swc",
    swc_version = LATEST_SWC_VERSION,
)

so perhaps be explicit and follow the same convention with LATEST_TYPESCRIPT_VERSION as the exported symbol with LATEST_VERSION around for backward compat and to be removed in 2.0?

[gregmagolan]

Should probably make the same change in rules_swc, rules_esbuild, rules_cypress & rules_deno

[jbedard]

Ok I've switched to the LATEST_*_VERSION style and marked the LATEST_VERSION to be removed in 2.0. If that looks right I'll do the same in other rulesets as well.

[gregmagolan]

🌮