Allow Dataset DOI in check permissions API request

[ErykKul]

What this PR does / why we need it:
It allows using a global identifier, e.g., doi, when checking permissions.

Which issue(s) this PR closes:

Closes #8994

[coveralls]

coverage: 20.047%. remained the same when pulling fcaeb27 on ErykKul:8994_permissions into 5fc7b30 on IQSS:develop.

[ErykKul]

The workaround here is to first get the dataset with the API, the response contains the technical (DB) ID that can be used (it does not contain slashes, it is an integer) to check the permissions.

[qqmyers]

The fix looks like it works for the case where the dataset PID exists, but it will return 500 errors instead of 404 when it isn't found or 400 for a missing ":persistentId" query param.

[sekmiller]

Hey @ErykKul, I'd like to pick this up but there's a merge conflict at the moment - so if you could resolve it I'll be able to test. Thanks!

[qqmyers]

Weird - the web editor to resolve the conflict shows 0 conflicts in that file...

[ErykKul]

@sekmiller @qqmyers I see that my PRs moved, but I am on vacation right now for another week, I will be back on 15th. I will re-merge the develop branch to them, do the necessary changes and retest once that I will be back at work. Some of them are open for quite some time, so they need some extra attention from me before merging, Thanks!

[ErykKul]

@sekmiller @qqmyers I had to manually merge the AbstractApiBean.java, but there where no conflicts to solve. Strange. It is now merged with the develop branch.

[sekmiller]

Hey @ErykKul This looks great. Thanks! The only thing I need you to do before I can merge it is for you to update the doc so that the url is in double quotes as in curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/admin/permissions/:persistentId?persistentId=$PERSISTENT_IDENTIFIER" - I would do it myself but I don't think I have permission.

[ErykKul]

@sekmiller Thanks for catching that! I have just added the missing double quotes.