Description
2.1.5 ran into a bad merge
2.1.6 ran into a build issue (shade had been modified to make the draft deletion script executable, but conflicted with our dockstore build)

This tests 2.1.7 zenodo client now with InvenioRDM endpoints that should really be namespaced into a separate tag/namespace

Review Instructions
Build, use, deploy to QA.
Try out zenodo operations

Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-7226

Security and Privacy

None

Please make sure that you've checked the following before submitting your pull request. Thanks!

• Check that you pass the basic style checks and unit tests by running mvn clean install
• Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
• Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
• If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
• Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
• Do not serve user-uploaded binary images through the Dockstore API
• Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
• Do not create cookies, although this may change in the future
• If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.