Add link sharing endpoint and modify community object for automatic DOI creation

[kathy-t]

Description
Webservice PR: dockstore/dockstore#5879

This PR adds the POST endpoint for creating shared access links using the description from https://inveniordm.docs.cern.ch/reference/rest_api_drafts_records/#create-an-access-link.

Also modifies the existing DepositMetadata Community object so that the id field is identifier to match the Zenodo API docs. The invenio deposit metadata docs don't have communities listed, but it is in its future directions section. The FAQ section of this post says that it should be backwards compatible.

Review Instructions
See dockstore/dockstore#5879

Issue
SEAB-6371 - link sharing
SEAB-5929 - automatic DOI creation

Security and Privacy

If there are any concerns that require extra attention from the security team, highlight them here.

e.g. Does this change...

• Any user data we collect, or data location?
• Access control, authentication or authorization?
• Encryption features?

no concerns

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.

[denis-yuen]

(security section and review missing, could be blanked in this case I guess)

[kathy-t]

Added a few more access link endpoints for deleting and getting a link. Re-requesting reviews

[denis-yuen]

review instructions ... could be blanked, can be reviewed as part of main ticket