Add tracing IDs in the status API

[PetarTodorovv]

Description
I noticed that in the status API we don't have tracing IDs(x-request-id, x-span-id, etc.). There is logic to load them from the context but seems we don't have the necessary middlewares which configure them. In the logs we have only formation-assignment-id and formation-id but they are extracted from the path parameters and added in the logs.

Example:

time="2024-05-30T10:43:55.671018513Z" level=info msg="Deleting formation assignment with ID: \"example-assignment-id\"" component="formationassignment/status_service.go:98:formationassignment.(*formationAssignmentStatusService).DeleteWithConstraints" formation-assignment-id=example-assignment-id formation-id=example-formation-id x-request-id=example-request-id
...
time="2024-05-30T10:43:55.757931815Z" level=debug msg="Executing DB query: DELETE FROM public.formation_assignments WHERE tenant_id = $1 AND id = $2" component="repo/delete.go:203:repo.(*universalDeleter).delete" formation-assignment-id=example-assignment-id formation-id=example-formation-id x-request-id=example-request-id

Changes proposed in this pull request:

• Add middlewares to the status API router that configure tracing IDs in the context and in the logger.

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: 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 [ivantenevvasilev]

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