Ready the first npm release #1

What remains before the first npm release, 0.1.0.

• Package metadata, README usage and OpenJDK notices.
• The JDK image split by module (jdk/<module>.jar), so pages fetch only the modules they use.
• java.desktop's headless parts in the image.
• OpenJDK regression tests beyond java/lang: java/net, java/security, javax/crypto, java/nio, java/util and more, 2,524 tests in test/jtreg/passing.txt, which the release workflow runs.
• Test workflow for pull requests and pushes to master.
• Release workflow: runs on release: published (not prereleases), checks the tag against package.json, runs pnpm jdk, the tests and the OpenJDK regression tests, then npm publish through a trusted publisher, with provenance.
• "private": true removed from package.json.
• Publish a placeholder 0.0.0 by hand to claim the name (npm only lets a trusted publisher be added to a package that exists). java-web was unavailable, so the package is @project516/java-web.
• Add the trusted publisher on npmjs.com: Project516 / java-web / release.yml.
• Publish the GitHub release v0.1.0; the release workflow published @project516/java-web@0.1.0 with provenance.
• Deprecate 0.0.0 and 0.0.0-stage.

Decision (2026-10-22): the license is AGPL-3.0-only, the package name is java-web, and npm publishing uses a trusted publisher (no stored token).

Decision (2026-10-22): the first release targets headless Java: console apps, libraries and javac. GUI apps (AWT, Swing) are out of scope for now.

Decision (2026-10-26): the image and the tests use one pinned JDK, the latest JDK 25 update, which pnpm jdk downloads; CI does the same, and Renovate bumps it.

Decision (2026-10-31): publish 0.1.0 by 2026-11-01, using the placeholder 0.0.0 to claim the name first.

Decision (2026-11-01): the package is @project516/java-web, since npm refused the unscoped name.