Preserve native message attributes when message is retried via ServiceControl

[SzymonPobiega]

Describe the suggested improvement

Is your improvement related to a problem? Please describe.

When a message that contains native attributes is retried via ServiceControl, the retried message does not contain the native attributes that the original message (ingested by ServiceControl) had

Additional Context

No response

[mauroservienti]

Discussed with Szymon

The transport can preserve message attributes (the native headers) when forwarding the message to ServiceControl. The issue is that ServiceControl won't store them because they are not part of the TransportMessage ingested by ServiceControl.

A hack could be the following:

• When the input queue pump picks up the message, it serializes the the MessageAttributes dictionary into the TransportMessage headers
• When the dispatcher dispatches a message, if there is no incoming message and there are the serialized message attributes, it means it's retrying a failed message in ServiceControl, and it'll restore the native message attributes; otherwise it'll remove them from the transport message headers (we don't want to copy those over to all outgoing messages)