chore: expose x-trace-id in response headers

[edmondbaloku]

• New feature
• Bug fix
• High impact

Description of work:
Frontend are showing the x-trace-id available from response headers in a api request, but as the resources and summary services did not expose the x-trace-id it was shown as null.

AB#56897

Testing:

• Can be tested
• Automatic tests created / updated
• Local tests are passing

Can be tested manually by looking at the response headers from any requests to the resources or summary api (absence request on landing page) and verifying that x-trace-id is under the access-control-expose-headers like this

access-control-expose-headers: Allow,x-fusion-retriable,x-trace-id

Checklist:

• Considered automated tests
• Considered updating specification / documentation
• Considered work items
• Considered security
• Performed developer testing
• Checklist finalized / ready for review