Enrich logger with additional tracing information

[PetarTodorovv]

Description
This PR aims to enrich the logger entries with additional information(formation-id and formation-assignment-id) when there are operations related to these entities. That will improve the logs and debugging and will help us to trace what happened a lot quicker/easier. Also, we already had the Istio distributed tracing headers/data in the context, with this PR I extend the logger info with that data too.

Changes proposed in this pull request:

• In the main locations/operations - create/delete formation, assign, unassign, resync, finalize mutation, and "status API" operations I added formation-id and/or formation-assignment-id entries with their respective IDs in the logger
• Created a couple of helper functions for the trace ID, span ID and parent span ID. And the logger was enriched with the mentioned IDs.

Related issue(s)

• ...

Pull Request status

• Implementation
• Unit tests
• Integration tests
• chart/compass/values.yaml is updated
• Mocks are regenerated, using the automated script

[kyma-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dzahariev, ivantenevvasilev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dzahariev,ivantenevvasilev]
• components/connectivity-adapter/OWNERS [dzahariev]
• components/connector/OWNERS [ivantenevvasilev]
• components/default-tenant-mapping-handler/OWNERS [ivantenevvasilev]
• components/director/cmd/scopessynchronizer/OWNERS [ivantenevvasilev]
• components/director/internal/domain/formation/OWNERS [ivantenevvasilev]
• components/director/internal/domain/formationassignment/OWNERS [ivantenevvasilev]
• components/director/internal/formationmapping/OWNERS [ivantenevvasilev]
• components/gateway/OWNERS [ivantenevvasilev]
• components/hydrator/OWNERS [ivantenevvasilev]
• components/instance-creator/OWNERS [ivantenevvasilev]
• components/kyma-adapter/OWNERS [ivantenevvasilev]
• components/operations-controller/OWNERS [dzahariev]
• components/pairing-adapter/OWNERS [dzahariev]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kyma-bot]

@PetarTodorovv: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pre-main-compass-gke-benchmark	6e64661	link	false	/test pre-main-compass-gke-benchmark

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.