Decide the JPMS story before adding module-info.java

[onacit]

There is no module-info.java, which is currently fine: the binder reflects into its own package,
which needs no opens, and the published jar becomes an automatic module, which is implicitly open,
so JAXB and JSON-B can reflect into the model types.

Tasks:

• if a module-info.java is ever added, it must opens com.github.jinahya.database.metadata.bind,
  or the XML and JSON bindings break at runtime;
• record that constraint next to the binding utilities so it is not discovered the hard way;
• fold this into the Align Java policy decision above.

---

Filed from _TODOS.asciidoc → Priority 5 - Build and Repository Hygiene → Decide the JPMS story before adding module-info.java``.
Maintainer notes are the source of truth for detail; this issue is the tracking record.