Implement Correlation IDs for Enhanced Logging and Tracing

[monilpat]

Is your feature request related to a problem? Please describe.

Currently, the logging system in our Cadence transactions lacks correlation IDs, making it challenging to trace requests across distributed systems and identify performance bottlenecks.

Describe the solution you'd like

Integrate correlation IDs into the logging framework used in Cadence transaction scripts, particularly in files like create_new_account_with_coa.cdc and transfer_erc20.cdc. This would involve:

• Generating unique correlation IDs for each transaction.
• Propagating these IDs across different transaction steps and services.
• Including correlation IDs in each log entry to facilitate end-to-end tracing.

Describe alternatives you've considered

• Using existing logging practices without correlation IDs, which limits the ability to trace and debug complex transaction flows.
• Relying solely on external monitoring tools, which might not capture all necessary context.

Additional context

Implementing correlation IDs will significantly improve observability and debugging capabilities, especially in distributed environments where tracking the flow of requests is crucial.

Related Issues

• Issue #141