Feature Request: API Get/Find Dataverses For Dataset and Dataverse Linking

[g-saracca]

Overview of the Feature Request

For the SPA Link Dataset feature we need a new API endpoint that returns the available dataverses for linking for the calling user.
After discussing with @sekmiller, I believe that to replicate the JSF behavior, the new endpoint should receive the query(collection name or alias -- that will be entered by the user) and the dataset identifier that want's to link.
Also instead of filtering from a query, an endpoint that just returns all the dataverses available for linking could work and we could filter in the frontend side.
Sek mentioned this filterDataversesForLinking method.

Update: @ekraffmiller also mentioned that we need similiar info for the dataverse linking. I've updated the title of the issue. See comment.

The API response could have below example format and return empty array [] if nothing found.

   [
      {
        id: 1,
        alias: 'dataverse-alias',
        name: 'Dataverse Name'
      },
      {
        id: 4,
        alias: 'foo',
        name: 'Foo'
      }
   ]

This is what we want to replicate 👇.

What kind of user is the feature intended for?
API Users

What inspired the request?
SPA Q3 Roadmap

What existing behavior do you want changed?
N/A

Any brand new behavior do you want to add to Dataverse?
New API endpoint.

Any open or closed issues related to this feature request?
This open PR is adding new specific permissions to Link Dataset/Dataverse.

[ekraffmiller]

One thing to keep in mind is that we need this list in two different features, for linking Datasets and for linking Dataverses.

• When linking a Dataset, the list of available Dataverses shouldn't include Dataverses where the Dataset is already linked.
• When linking a Dataverse, the list of available Dataverses shouldn't include Dataverses where the Dataverse is already linked.

[g-saracca]

Thanks for pointing this out @ekraffmiller, could be nice to have one single endpoint for both purposes maybe.