feat: "Link Dataset/Dataverse" permission (now with Flyway migration script)

[vera]

What this PR does / why we need it:

This is a resubmission of #11534:

Linking or unlinking a dataset or dataverse now requires the new "Link Dataset/Dataverse" permission.
Previously, this action was covered by the "Publish Dataset/Dataverse" permission.
Linking and publishing permissions can now be granted separately, allowing for more fine-grained access control.

This resubmission now includes a SQL file to migrate the permissionbits column in the dataverserole table:

We're adding new permissions at bit 13 (4096 LinkDataverse) and bit 14 (8192 LinkDataset).
They should be set for any role that has the permission in bit 11 (1024 PublishDataverse) and bit 12 (2048 PublishDataset),
respectively.
We also need to move the permissions with current bits 13-14 to bits 15-16 to make room for the new permissions.

https://github.com/vera/dataverse/blob/00a45f525f34fc2d9dce3104c4ff16c10fe6c534/src/main/resources/db/migration/V6.6.0.4.sql#L1-L4

I've tested the SQL migration file and it correctly migrates the permission bits:

Before:

 id |      alias      |                                                        description                           |            name             | permissionbits | owner_id 
----+-----------------+----------------------------------------------------------------------------------------------+-----------------------------+----------------+----------
  1 | admin           | A person who has all permissions for dataverses, datasets, and files.                        | Admin                       |          16383 |         
  2 | fileDownloader  | A person who can download a published file.                                                  | File Downloader             |             16 |         
  3 | fullContributor | A person who can add subdataverses and datasets within a dataverse.                          | Dataverse + Dataset Creator |              3 |         
  4 | dvContributor   | A person who can add subdataverses within a dataverse.                                       | Dataverse Creator           |              1 |         
  5 | dsContributor   | A person who can add datasets within a dataverse.                                            | Dataset Creator             |              2 |         
  6 | contributor     | For datasets, a person who can edit License + Terms, and then submit them for review.        | Contributor                 |           8280 |         
  7 | curator         | For datasets, a person who can edit License + Terms, edit Permissions, and publish datasets. | Curator                     |          11103 |         
  8 | member          | A person who can view both unpublished dataverses and datasets.                              | Member                      |             28 | 

After:

 id |      alias      |                                         description                                          |            name             | permissionbits | owner_id 
----+-----------------+----------------------------------------------------------------------------------------------+-----------------------------+----------------+----------
  1 | admin           | A person who has all permissions for dataverses, datasets, and files.                        | Admin                       |          65535 |         
  2 | fileDownloader  | A person who can download a published file.                                                  | File Downloader             |             16 |         
  3 | fullContributor | A person who can add subdataverses and datasets within a dataverse.                          | Dataverse + Dataset Creator |              3 |         
  4 | dvContributor   | A person who can add subdataverses within a dataverse.                                       | Dataverse Creator           |              1 |         
  5 | dsContributor   | A person who can add datasets within a dataverse.                                            | Dataset Creator             |              2 |         
  6 | contributor     | For datasets, a person who can edit License + Terms, and then submit them for review.        | Contributor                 |          32856 |         
  7 | curator         | For datasets, a person who can edit License + Terms, edit Permissions, and publish datasets. | Curator                     |          43871 |         
  8 | member          | A person who can view both unpublished dataverses and datasets.                              | Member                      |             28 |      

Which issue(s) this PR closes:

• Closes Feature Request: Separate "link" permission from "publish" permission #11690

Special notes for your reviewer:

/

Suggestions on how to test this:

I've extended an existing test which can be run with mvn test -Dtest="DatasetsIT#testCreateDeleteDatasetLink" to check that datasets cannot be linked/unlinked unless you have the curator role, which has been altered to include the new link permissions.

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

I've added a short release note.

Additional documentation:

/

[coveralls]

coverage: 23.232% (+2.5%) from 20.726%
when pulling cb2df1a on vera:feat/link-permission
into 20aaf5a on IQSS:develop.

[sekmiller]

You'll need to rename this script to 6.7.1.0

[pdurbin]

Well, 6.7.1.1 since we start at 1.

Also, heads up that this PR is in a race with PR #11654 for that number. 😄

[vera]

Well, let's see if I make it :) done.

[sekmiller]

Looks good. One minor issue - you'll need to update the name of the script because this will go in after the release of 6.7.1

[ofahimIQSS]

approving version bump

[ofahimIQSS]

tests passed - performed additional regression testing in internal. merging!