Add use case for getting list of collections a user may create datasets in

[vera]

What this PR does / why we need it:

This PR adds code for getting the list of collections a user may create datasets in.

Which issue(s) this PR closes:

/

Related Dataverse PRs:

/

Special notes for your reviewer:

/

Suggestions on how to test this:

I've added tests and docs on how to use.

Is there a release notes or changelog update needed for this change?:

Yes

Additional documentation:

/

[ekraffmiller]

Hi @vera thanks for your PR! I was just reviewing the API that this use case is wrapping, and it has some issues with it - it doesn't have a paging option, and if the endpoint is called for a user such as an admin that returns a long list of collections, the performance is not good.
We have a more general API, /mydata/retrieve, that takes parameters for paging, dvObject type, roles, and also allows filtering of the results by collection name. It's the API used in the MyData page to filter the table contents. With the right parameters, it can return a list of collections that a user can create a dataset in. Could that be used for your purposes instead? We are thinking we might deprecate the collectionList endpoint in favor of mydata/retrieve.

UPDATE: after talking to the team, we think it's better to keep collectionList as a separate API, and add pagination and filtering to it. I created an issue for it here: IQSS/dataverse#12423