DD-2318: spilt terms of use and access

[jo-pol]

What this PR does / why we need it:

Preparations for file specific licenses or terms of use.

Which issue(s) this PR closes:

• Closes #

Special notes for your reviewer:

• New TODO’s in the changed sources, don't forget the load diff-s for files with too many changes.
• New/changed validation classes
• Safeguards (preventing NPEs) in command input validation. It might touch functionality.

Suggestions on how to test this:

• check out dans-core-system at least at 64a840ff ... on 7/27/26 at 1:25 PM

• Build and on the DANS VM dev_dataversenl_v6.10-PATCH-7_2026-07-19.box

  deploy.py --dataverse-war external/dataverse/target/dataverse dev_dataversenl
  

• The deploy above runs the flyway script if not done by a previous deploy.
  For manual test of the flyway script, see: DD-2317: split table TermsOfUseAndAccess #247
  Note that the name and content of the script changed.

• Visit the web-UI of the VM and show a dataset

• Upload a file, save the changes, restrict its access.

• Edit terms of the same dataset, select 'custom terms' as license and fill fields in both groups.

• Publish the changes.

• Edit terms of the same dataset and publish again.

• VM patch 11 requires creation of a dataset, the above changes work, also resetting the the custom terms to CC0 and un-restrict the files.

• Creating and using a template with both types of terms works.

• The web-ui does not seem to touch constructors nor execute methods of UpdateDatasetLicenseCommand or UpdateTermsOfAccessCommand so all commands touched by this PR should be tested:

  • https://guides.dataverse.org/en/latest/api/native-api.html#update-dataset-terms-of-access
  • https://guides.dataverse.org/en/latest/api/native-api.html#update-dataset-license
  • UpdateDatasetFieldsCommand
  • https://guides.dataverse.org/en/latest/api/native-api.html#restrict-files
  • https://guides.dataverse.org/en/latest/api/native-api.html#publish-a-dataset
  • FinalizeDatasetPublicationCommand
  • https://guides.dataverse.org/en/latest/api/native-api.html#create-a-template-for-a-collection
  • CuratePublishedDatasetVersionCommand

• Scenarios for validation errors.

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: