Automated release verification

[vreynolds]

Release 10.0.0 had some issues

As a future-proofing measure to catch broken layer versions before customers, add a verification step after the aws publish-layer-version step (layer versions are relatively cheap, so not worth it to set up a pre-release infrastructure at this point).

Non-directive ideas:

• we can have a test lambda function in our telemetry-sandbox account, configured to export telemetry (consider adding the function source and deploy code to a repo, so it's easy to re-create if necessary)
• as a follow-up to the publish-aws job, we add a job that updates the layer on the test function to the new version
• we invoke the test function a few times
• we verify that honeycomb received data within some timeout window but curling the query data API