Lookup dataverse by alias or ID when downloading guestbook responses via API

[bencomp]

What this PR does / why we need it:
Replaces a dataverse by-alias lookup with findDataverseOrDie to allow looking up a dataverse by both its alias and its ID, as the documentation for 5.12.1 mentions. The same section for the latest version says the same.

Which issue(s) this PR closes:

• Closes input database ID for Retrieve Guestbook Responses for a Dataverse Collection #9619
• Closes API endpoint for downloading guestbook doesn't accept the Dataverse Collection's database ID, accepts only its alias #8563

Special notes for your reviewer: I would like this PR to count towards my Hacktoberfest goal, so if this is useful, please add the hacktoberfest-accepted label or an approving review.
My editor VSCodium with Java extensions made me handle the WrappedResponse that findDataverseOrDie may throw. Throwing a WebApplicationException is appropriate for the context, according to its Javadoc description.

Suggestions on how to test this: check that the commands in the issue work after applying the change.

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?:
I suppose this may fix a bug in the API, but I don't consider this a big change otherwise.

Additional documentation:

[pdurbin]

@bencomp thanks for the PR! 🎉 I left a comment about WrappedResponse.

[pdurbin]

Asking about tests.

[pdurbin]

Do you feel like writing some tests? If so, I'd suggest adding a method for downloading guestbook responses to UtilIT.java (I couldn't find one) and then calling it from DataversesIT.java.

[bencomp]

Working on it.

[bencomp]

I couldn't test locally – maybe because I have en_GB as locale – and the Maven integration test job doesn't run the new test either. Does that require something else to happen, @pdurbin?

[pdurbin]

@bencomp thanks for adding tests! To run tests locally, I recommend running Dataverse in Docker using https://guides.dataverse.org/en/6.0/developers/dev-environment.html#quickstart and then running just the tests in that class with mvn test -Dtest=DataversesIT. You could get even more granular with mvn test -Dtest=DataversesIT#testGetGuestbookResponses.

Jenkins is failing but not due to your code. I just kicked off a manual run at https://github.com/gdcc/api-test-runner/actions/runs/6554508063 to get a second opinion.

[pdurbin]

This should help resolve the 403.

[pdurbin]

I just looked over https://guides.dataverse.org/en/6.0/api/native-api.html#retrieve-guestbook-responses-for-a-dataverse-collection and it seems fine. It already claims to support a collection alias, which is what @bencomp is enabling in this PR.

[bencomp]

Well, now it works on my machine 🎉
I would say this is done 😌

[pdurbin]

Jenkins is still broken right now but I'm getting a second opinion about if API tests are passing here: https://github.com/gdcc/api-test-runner/actions/runs/6561459544

Should take about 20 minutes.

[pdurbin]

Ok, it passed. @scolapasta can we put this on https://github.com/orgs/IQSS/projects/2 ?

[pdurbin]

Tests are passing on GitHub Actions and the docs at https://guides.dataverse.org/en/6.0/api/native-api.html#retrieve-guestbook-responses-for-a-dataverse-collection look good. They already mention alias even though it's newly supported in this PR.

Thanks, @bencomp! 🎉