Message sequencing and traceability in failure/retry situations

### Problem description
When Guardian is producing hedera transactions sometimes they need to be chunked and submitted independently. If one of the chunk submission fails for some reason the system seem to be losing track of sequencing. For example

- https://testnet.mirrornode.hedera.com/api/v1/topics/0.0.48009739/messages/23783 1 of 3
- https://testnet.mirrornode.hedera.com/api/v1/topics/0.0.48009739/messages/23784 2 of 3

but

- https://testnet.mirrornode.hedera.com/api/v1/topics/0.0.48009739/messages/23785 is a new document

If this indicates that something has failed in IPFS accepting the 3 of 3 for 23785, as there is no other implicit way of defining the chain here which this breaks traceability.

### Step to reproduce
See above

### Expected behavior
Ability trace the sequence of messages - when they retried and succeeded it is possible to link them together

### Screenshots
N/A - see description.