Protect corellationId from duplication or updation within same request
As part of producing status messages ADR #80 we have proposed that every service now will produce the status messages to be able to track the e2e status of dataflow.
@rostislav.dublin has highlighted that we must make sure that corellationId which will flow with every request to stich the complete dataflow status messages with each other should be protected so that no one should tamper it or by mistake generate other corellationId which might overlap with others..
Creating this issue to discuss over that topic and comeup with some optimal solution to tackle this situation.
This was highlighted in this MR osdu/platform/system/lib/core/os-core-common!93 (merged)