feat: pass 'correlation-id' from client to SeismicStore http request header

Type of change

• Bug Fix
• Feature
• Pipeline
• Test

Does this introduce a change in the core logic?

• No
• Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this follow conventional commits spec?

• No
• Yes

Have you set the target Milestone?

• No
• Yes

Have you set the no-detached-pipeline label?

• No
• Yes

Updates description?

Pass 'correlation-id' when present in client's call parameters to SeismicStore http request header