Update publish plan resolver for EZID registration

[briri]

• We are giving an ID to plans when they’re created now, but we need to not publish to EZID until it is registered by user
• Add new Data Source for EZID, update Publish Plan resolver to call that

[bofstein]

When EZID registration is successful, set registered timestamp in the registeredByid

[briri]

We are going to just refactor the existing EZID Lambda function (port it over to the dmptool-infrastructure repo) instead of pulling that logic into the Apollo code.

This will allow us to leverage the SQS / EventBridge infrastructure. See #58 for details.

Copy over the existing Lambda function so that its now managed by the dmptool-infrastructure repo and using the new system's resources.

It should be triggered by an EventBridge listener rule.

The Listener rule should:

• Subscribe to messages with a detail_type of dmp_ezid_sync
• Allow 5 retries
• Send failures to the DeadLetterQueue

The Lambda code should:

• Query SSM Parameter store for /uc3/dmp/tool/[env]/EzidPaused.
• If the value is not zero (then it is the number of minutes to pause):
  • Call the SQS API to ChangeMessageVisibility for the current message to the number specified (think we need to convert to seconds). This will "hide" the message until the time expires. After that it will become "visible" again in the queue and get processed.
• Otherwise (it is zero):
  • Fetch the latest version of the DMP from the DynamoDB table using the dmpId in the message
  • Transform the DMP JSON into an EZID JSON message
  • Send the JSON message to the EZID API

Most of this logic can be lifted directly from the old Lambda function. Convert it to nodeJS though.

We will also want a 2nd Lambda function that checks each registered plan and ensures that EZID has the latest version of the plan. This function can be used to ensure fidelity of records in the DMP Tool and EZID.

It should be triggered by an EventBridge listener rule.

The Listener rule should:

• Subscribe to messages with a detail_type of full_ezid_sync
• Allow 1 retry
• Send failures to the DeadLetterQueue

The Lambda code should:

• Query the RDS database for the list of all plan that are registered and fetch their dmpIds
• Send an SQS message to trigger a sync for that DMP.

The message should use a "detail_type": "dmp_ezid_sync", "detail": { "dmpId": "https://doi.org/10.11111/A1B2C3D4" }.