update getCollectionMetadataBlocks use case to support passing a dataset type

[pdurbin]

What this PR does / why we need it:

The promise of a dataset type has been that if you link a metadata block with it (e.g. linking CodeMeta to a software type), those extra fields will be available to you (displayed on create) when you create a dataset.

Which issue(s) this PR closes:

• Closes extend the getCollectionMetadataBlocks use case to allow passing datasetType #210

Related Dataverse PRs:

• Builds upon this PR, which should be tested and merged first: Update CreateDataset use case to allow non-default dataset types #373

Special notes for your reviewer:

The existing code doesn't have any tests that I could find. yolo!

If you point me to the tests I'm happy to edit them.

If you want me to write tests from scratch, I'm happy to do that too. 😄

Suggestions on how to test this:

First, add a dataset type called "foobar" that's associated with a non-citation metadata block like geospatial.

Then, try something like this:

const getBlocks = await getCollectionMetadataBlocks.execute(':root', true, 'foobar')
console.log(getBlocks);

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

Yes, coming.

Additional documentation:

None.

[ofahimIQSS]

tests passing - merging PR