Authorization migrate xsd to classes

[mikejritter]

What does this do?

• Removes hyperjaxb plugin from the authorization jaxb module
• Create classes for what was previously schema generated
• Add jspecify for some null safety

Why are we doing this? (with JIRA link)
Jira: https://collectionspace.atlassian.net/browse/DRYD-2074

This migrates both the JPA entities and JAXB models as we are not migrating to jakarta persistence yet, so using the plugin for code gen is no longer available afaik (you can do either all javax or all jakarta).

JSpecify has been added in order to start to help understand what can/cannot be null. At the moment, I only added NonNull to the List getters in order to reflect previous behavior.

How should this be tested? Do these changes have associated tests?

• On dev:
  • Compile the authorization/jaxb module
  • copy the generated sources to a separate directory (e.g. diff)
• switch to this branch
  • compare the old generated classes to the new classes, e.g. git diff --no-index <(cat diff/org/collectionspace/**/*.java) <(cat src/main/java/org/collectionspace/**/*.java)
  • mvn clean compile should pass (might have dependencies which need to be compiled as well)

Dependencies for merging? Releasing to production?
Still more modules to migrate + other javax to jakarta import migration before compilation will be possible.

There's also an old Aspect which we should look at once the migrations are finished (JaxbXMLGregorianCalendarMarshal).

Has the application documentation been updated for these changes?
n/a

Did someone actually run this code to verify it works?
@mikejritter has been testing locally

[mikejritter]

After merging I found another field access for something which is now private. Will be fixed in the PR updating javax imports.