11710 find dataverses for linking

[sekmiller]

What this PR does / why we need it: Adds a new api endpoint which may be used to retrieve a list of Dataverse Collections to which a given Dataset or Dataverse Collection may be linked. The end point also takes in a search term which currently must be the start of the collections' names.

Which issue(s) this PR closes:

• Closes Feature Request: API Get/Find Dataverses For Dataset and Dataverse Linking #11710

Special notes for your reviewer:
One piece of new functionality is adding a search feature to the query on permissions - so that you can pass a search term along with a user and permission to further filter the collections returned.
The also fixes an unrelated test for retrieving a Dataverse Collection's Templates. In an existing database if there are templates created in Root then those templates will be inherited by any collection that is a child of Root that also shares Root's metadata blocks.Since the test asserts that only the newly created template should be available to the collection the inherited template causes a failure. I updated the test so that the child dataverse will have different metadata blocks than Root so that the only template available is the one created in the child as assumed by the test.
Also changed the name of findDvoByIdAndFeaturedItemTypeOrDie since I used it here and it really doesn't depend on the dvObject being a featured item.
Also added a new json object builder for dataverses which only returns the id, alias and name of the dataverse, this was needed to return the response suggested in the ticket.

Suggestions on how to test this: Try the new api endpoints and verify that the expected collections are returned.
-The end point also takes in an optional search term which is tested against the collections' names.

• Try it with a blank search term and a large database - near prod if possible to test for performance.
  -The user calling this API must have Link Dataset or Link Dataverse permission on the Dataverse Collections returned and given the object type.
  -there is also a queryParam for "alreadyLinked" which returns a list of dataverses to which the queried dvObject (either dataset or dataverse) is linked, to be used for unlinking. (Only those collections that the requester has linking permissions will be returned.
• also for performance - test with a superuser who will have perms on all collections.
  -If the Collection has already been linked to the given Dataset or Collection, it will not be returned.

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

Is there a release notes update needed for this change?:
-included
Additional documentation:
docs added under native api

[coveralls]

coverage: 23.517% (-0.02%) from 23.538%
when pulling 0982ff2 on 11710-find-dataverses-for-linking
into 56bf628 on develop.

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:11710-find-dataverses-for-linking

ghcr.io/gdcc/configbaker:11710-find-dataverses-for-linking

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

[ofahimIQSS]

11710server.log
looks good, merging