Add trace context in Sidekiq to connect request transaction and worker in the one trace

[dixent]

What does this pull request do?

1. Adding transaction trace context in the Sidekiq job.
2. Use transaction trace context when creating transactions for Sidekiq job by the Sidekiq server.

Why is it important?

Connection of transactions in one trace is necessary to display data in Kibana. It allows jumping from one transaction to another even if one worker calls another.

Checklist

• I have signed the Contributor License Agreement.
• My code follows the style guidelines of this project (See .rubocop.yml)
• I have rebased my changes on top of the latest main branch

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

• I have made corresponding changes to the documentation
• I have updated CHANGELOG.asciidoc
• I have updated supported-technologies.asciidoc
• Added an API method or config option? Document in which version this will be introduced

Related issues

https://discuss.elastic.co/t/distributed-traces-on-background-jobs/256555

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
9609fa1, d49cd45

Please, read and sign the above mentioned agreement if you want to contribute to this project

[dixent]

I am sorry, I am waiting assist from my company management regarding CLA.