build: define typescript version via string in module.bazel file (angular#63431)

Within our module.bazel file when describing the version of typescript to use for rules_ts, we use ts_version instead of ts_version_from to prevent our package.json file from being
part of the set of files used to calculate the sha for the lock file.  Any unrelated change to the version of the typescript file would end up causing our lockfile to be out of date.
This amount of churn has proven to be too much for our current setup. We instead now test to validate the versions defined in the package.json and MODULE.bazel files match.

PR Close angular#63431

Author: josephperrott

BUILD.bazel

@@ -1,4 +1,5 @@
 load("@aspect_rules_js//js:defs.bzl", "js_library")
+load("@devinfra//bazel/validation:defs.bzl", "validate_ts_version_matching")
 load("@npm//:defs.bzl", "npm_link_all_packages")
 load("//:yarn.bzl", "YARN_PATH")
 load("//tools:defaults.bzl", "copy_to_bin", "js_binary")
@@ -11,7 +12,6 @@ exports_files([
     "browser-providers.conf.js",
     YARN_PATH,
     "package.json",
-    "angular.json",
 ])
 
 npm_link_all_packages(
@@ -25,6 +25,11 @@ filegroup(
     srcs = ["package.json"],
 )
 
+validate_ts_version_matching(
+    module_lock_file = "MODULE.bazel.lock",
+    package_json = "package.json",
+)
+
 alias(
     name = "tsconfig.json",
     actual = "//packages:tsconfig-build.json",

MODULE.bazel

@@ -104,7 +104,7 @@ rules_ts_ext.deps(
     name = "angular_npm_typescript",
     # Obtained by: curl --silent https://registry.npmjs.org/typescript/5.9.2 | jq -r '.dist.integrity'
     ts_integrity = "sha512-CWBzXQrc/qOkhidw1OzBTQuYRbfyxDXJMVJ1XNwUHGROVmuaeiEm3OslpZ1RV96d7SKKjZKrSJu3+t/xlw3R9A==",
-    ts_version_from = "//:package.json",
+    ts_version = "5.9.2",
 )
 use_repo(rules_ts_ext, **{"npm_typescript": "angular_npm_typescript"})