Automate Checking with AspireCloud

[Ipstenu]

Check with Aspire to make sure all the information is correct.

Chuck said this can be automated :)

[bensternthal]

@Ipstenu can you provide more details on this one?

[cdils]

Context: When a new version of FAIR Connect is released, ensure that AC is retuning the new version

[chuckadams]

I think there's basically two items to do here:

1. Update the release checklist for Connect for someone to verify by hand that AC sees the update. Possibly include kicking the AspireSync job to start a sync immediately so we're not waiting up to an hour for that to happen.
2. Automate that process.

Automating the check is as simple as polling the package metadata endpoint on AC, it's pushing the update in a timely fashion that's a bit tricky: this is semi-related to the "federate my package" protocol we need to come up with for Beacon, but for advertising updates to an existing Repository rather than enrolling a new one.

Right now the obvious solution for updating AC immediately is to push the package metadata straight to AC. The problem with that is that it requires admin-level authority, since AC implicitly trusts the pushed data and doesn't check signatures (or have any way of doing so). But if it instead just pinged AC with the package DID, then AC could chase down the chain from the DID doc to the repository (e.g. Beacon) and retrieve and verify the metadata from there. If we limit it to only updating DIDs that are already indexed and don't allow them to change the slug, then we limit any potential hijacking.

[cdils]

@cdils to add this to release checklist, per 1.