Lambda Extension - Implement Serialize for LambdaTelemetryRecord #757
Description
When using an events processor on a lambda extension, you get a vector of LambdaTelemetry structs, which in turn contain a LambdaTelemetryRecord enum, which has a large number of variants.
In cases where for the most part you expect to simply forward those records on as, say, JSON, it currently requires the user to write their own Serialize implementation. With the telemetry data conforming to the OTEL standard, would it not be desirable to have a standard serialization for the telemetry records?
Are there any reasons why this might not desirable? If there are no objections to having a standard serialization I might have a go at this myself. Any comments appreciated!