split table terms of use and access

[jo-pol]

What this PR does / why we need it:

This PR prepares the Dataverse codebase for file-specific licenses/terms by splitting the legacy model “TermsOfUseAndAccess” into two separate models (“TermsOfUseOrLicense” and “TermsOfAccess”) and updating persistence, API, UI, and tests accordingly.

Changes:

• Introduces new termsofaccess and termsofuseorlicense tables (Flyway) and updates entity mappings and references.
• Updates API/commands/JSON export-import paths to read/write the new split terms objects.
• Updates UI (xhtml), exporters, and test fixtures to reflect the new model.
• Added validation tests to DatasetVersionTest

Which issue(s) this PR closes:

• Closes #

Special notes for your reviewer:

Suggestions on how to test this:

• See my cheat sheet for a DANS VM of v6.11 https://github.com/DANS-KNAW-jp/dataverse/blob/DD-2318-spilt-termsOUAA/tests/shell/DANS-v6-10/restrict-file.sh

• These test clearly did not cover code flagged by Codepilot DANS-KNAW-jp@cf45fb2

• between v6.10 and v6.13 new classes are introduced using the old TermsOfUseAndAccess. We have no means to test the changes.

• Should I still have missed something: null pointer exceptions usually meant an omission in pairs of lines like

            termsOfAccess.setXxx(obj);
            objXxx.setTermsOfAccess(termsOfAccess);
  
            termsOfUseOrLicense.setXxx(obj);
            obj.setTermsOfUseOrLicense(termsOfUseOrLicense);
  

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Yes, a DB table is split into two tables and its references needs updates, so:

Upgrading requires a maintenance window and downtime. Please plan accordingly, create backups of your database, etc.

Additional documentation: