Include payload in term advisories

Proposed change

Termination advisories include all the message data to help one find the message in the stream that holds the message, but:

1. Streams can be removing messages from due to limits meaning the ability to fetch the data might be short lived
2. It's expensive to go feetch the message to build something like a DLQ

The proposal is to include all the original message data in the term advisory - original timestamp in addition to the timestamp the event was create and most importantly the origianal message payload.

Use case

One can read these advisories and build a full DLQ that holds payload and all without aditional API integrations.

Contribution

No response