11772 api terms of access

[sekmiller]

What this PR does / why we need it:
Adds an api to allow the user to update the terms of access for restricted files of a given dataset

Which issue(s) this PR closes:

• Closes API: Restricted Files & Terms of Access in the dataset #11772

Special notes for your reviewer:
The json parser creates a terms of use and access object that only includes terms of access items. In the command the dataset's existing license and terms of use are merged with the updated access items.

Suggestions on how to test this:
The api endpoint is: curl -H "X-Dataverse-key:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -X PUT "https://demo.dataverse.org/api/datasets/3/access" -H "Content-type:application/json" --upload-file access.json

where access.json would look like this:
{
"customTermsOfAccess": {
"fileAccessRequest": true,
"termsOfAccess": "Your terms of access for restricted files",
"dataAccessPlace": "Your data access place",
"originalArchive": "Your original archive",
"availabilityStatus": "Your availability status",
"contactForAccess": "Your contact for access",
"sizeOfCollection": "Your size of collection",
"studyCompletion": "Your study completion"
}
}

make sure that the custom terms of use and/or license of the dataset are left unchanged.

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?: included

Additional documentation: added to native api docs

[coveralls]

coverage: 23.549% (+0.008%) from 23.541%
when pulling 1252f38 on 11772-api-terms-of-access
into 89813b7 on develop.

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:11772-api-terms-of-access

ghcr.io/gdcc/configbaker:11772-api-terms-of-access

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.