Identify the contents of the payload for publish and payload atomicity

[rhysrevans3]

No description provided.

[lliming]

There are multiple components of the payload.

• Authorization provenance - the basis for the STAC ingest service's (STAC API Transaction extension's) authorization decision, so we can troubleshoot auth policy configuration
• Publisher provenance - details about the ESGF publisher software used for the action (e.g., version), so we can guard against obsolete publisher software
• Catalog content - the details of the collection, item, or asset being acted on

Please see https://github.com/ESGF/esgf-roadmap/blob/main/core_architecture/event_schema.md (specifically, the publish action) for a proposed example of the authorization provenance

[lliming]

It seems likely we'll also need some info about CV validation (e.g., versions of CVs used for validation) in the event schema. Let's confirm what we think is necessary to support troubleshooting.