Add use cases to get the zip download limit and embargo duration in months

[GPortas]

What this PR does / why we need it:

We need these new cases since they are necessary for the SPA to show the related functionality.

Which issue(s) this PR closes:

• Closes Add use case to read settings required by the SPA (Embargo enabled and zip download limit) #84

Related Dataverse PRs:

• Depends on Dataset files API extension for file counts dataverse#9853
• Depends on Add getZipDownloadLimit and getMaxEmbargoDurationInMonths API info endpoints dataverse#9881

Special notes for your reviewer:

Tests related to files are failing, since the Dataverse branch they are pointing to does not have the files API extension. Therefore, this PR must wait for the PR IQSS/dataverse#9853 to be merged and IQSS/dataverse#9881 to be updated with develop.

Suggestions on how to test this:

• Visual inspection of the code
• Check unit and integration tests execution in GitHub actions

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

Add GetZipDownloadLimit and GetMaxEmbargoDurationInMonths use cases

Additional documentation:

None

[MellyGray]

Looks good. Just a comment about splitting a test

Hopefully the dataverse branches this PR depends on get merged soon

[GPortas]

@MellyGray

There are use cases whose integration tests are failing, that is normal, since the Dataverse branch used in this PR does not include all endpoints due to Dataverse PRs not yet merged.

[MellyGray]

There are use cases whose integration tests are failing, that is normal, since the Dataverse branch used in this PR does not include all endpoints due to Dataverse PRs not yet merged.

@GPortas I know, but should the integration tests point to DATAVERSE_IMAGE_TAG=9880-info-zip-download-limit-embargo ? branch 9880 is already merged into develop so maybe you can point to the develop image tag so when the other files PR get merged into develop the integration tests work

I'm ready to approve this, just wanted to comment that

[GPortas]

@MellyGray

I agree. In fact, in an ideal scenario the develop branch of this repository should always point to dataverse develop branch image (unstable tag).

Updating.

[MellyGray]

LGTM 👍