[wmdietl]

Brings the typetools Checker Framework 3.53.0 release into master. The import itself was reviewed and merged in #2197. Please merge this pull request with a merge commit, with the subject typetools/checker-framework 3.53.0 release (#2198) and an empty body, so that the typetools commits keep their authorship.

The 31 commits of 3.50.0 that the import of 3.50.0 (#2186) did not contain

I computed these by comparing the commits of 3.49.5..3.50.0 with the commits of #2186. They are in one commit here, because this pull request is merged without squashing: its message has the authors as Co-authored-by lines and says what has an effect. 28 of the 31 change nothing; the three with changes are below.

• Empty, our tree is newer or has its own: the 17 dependency and plugin updates (Shadow 8.3.8 and 8.3.9, Spotless 7.1.0 to 7.2.1, Error Prone 2.40.0 and 2.41.0, Gradle 8.14.3, commons-io, classgraph, the AWS bom, gradle-git-properties, bnd, commons-lang3 in the Maven example), "Update the Shadow plugin", "Consolidate Java version checking" (EISOP has its own useJdkVersion scheme), "Run Compiler Messages Checker" (ours defines the check in framework and checker, the only modules with messages.properties), "Use new location for releasing to Maven central" (ours already uses the new URLs), "Don't try to install ruff or mypy" (our CI image has no ruff), "Remove extra repositories block", "Add comment to top-level Makefile", "Fix formal parameter type", the two release stamps ("Prep for next release", "new release 3.50.0"), and the two commits that were already present.
• Applied: the typo fixes in the release README, "Update .gitignore file" (the union of our entries and typetools' new ones), and "Don't add allDataflowTests as a dependsOn to all test tasks". The last one means :dataflow:test no longer runs allDataflowTests; nonJunitTests and allTests still do, as in typetools.
• Partly applied: "Fixes to the release scripts". Our reworked scripts already have most of it. I did not take the hunk that comments out ensure_group_access(DEV_SITE_DIR), which works around a problem on typetools' own server.

Other changes

• Version catalog: adopts typetools' "Use version catalog" (imported only as an unused file in typetools/checker-framework 3.53.0 release #2197) with our versions. The versions of the plugins and libraries are in gradle/libs.versions.toml, and the build files refer to them as libs.*. This replaces the library versions in gradle.properties that were adopted from typetools' earlier commit. The names follow typetools' catalog; guava is the annotated Guava as in typetools, and the unannotated one is google-guava. The resolved dependencies of every subproject (334 lines, checked before and after) and the versions of all plugins do not change.
• Markdownlint configuration: .markdownlint-cli2.yaml is restored; typetools removed it when it moved to pymarkdownlnt, and our Makefile still has the targets that read it.

Still open

• Whether to adopt uv (typetools' Makefile runs ruff and ty through uvx, which our CI image does not have).
• Making the Markdown files conform so that markdownlint-check can join style-check, and the python-typecheck target.
• The annotated JDK: eisop/jdk pull requests Merge stores after expression statements #158 (README, master, JDK 17) and Store paths for artificial trees #159 (jdk-21: typetools/jdk up to 3.53.0 and master).

Tested: tasks --all, compileJava, compileTestJava, assembleForJavac, a zip/copyToWebsite dry run, and the full :dataflow:test, :dataflow:allDataflowTests, :framework:test and :checker:test suites pass on JDK 21; spotlessCheck, ruff, requireJavadoc and javadocDoclintAll (on changed lines) are clean. CI covers the rest.

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.