Refresh project/POM metadata while preserving historical authorship and bundle identities

[jmanico]

Reviewed 2026-09-25 (America/Los_Angeles) against main at bd249f5. Execution order and cross-issue ownership: #169. Batch 05.

This scope replaces the dated implementation prescriptions in the original report and earlier comments; linked historical evidence remains useful but must be rechecked before implementation.

• Align organization naming and public project documentation URLs with current authoritative OWASP records; verify useful URLs at implementation time.
• Align active maintainer roles/contact IDs with current README/MAINTAINERS.md and OWASP leader records, retaining original-author attribution instead of deleting historical contributors.
• Set appropriate Bundle-Vendor/Bundle-DocURL metadata without changing Constrain OSGi imports to actual adapter API requirements and freeze bundle identities #137's frozen Bundle-SymbolicName or existing JPMS identities.
• Verify all four generated manifests and parent/module POM metadata; keep dependency scopes, bytecode and APIs unchanged.
• Add the metadata check to Modernize release tooling and validate future releases without replacing 1.4.1 #95's future-release checklist. Do not require rewriting the already signed 1.4.1 POM/assets or claim a future metadata fix is already on Central.

README already names Jim Manico and Jeremy Long (#159/#164). Broader source/license notices belong to #124, not a blanket metadata replacement.