propagate trace.id to http response log manually

[mshustov]

Summary

Closes #114476
http.server.response logs are emitted when an APM transaction was finished, therefore it contains unrelevant trace.id value.
APM agent is going to extend Hapi lifecycle instrumentation (tentatively in v8.1.0) elastic/apm-agent-nodejs#2353
Until it's resolved in the upstream, we can work it around by storing trace.id for every incoming request.
Kibana logs with this change (a short version for brevity) look like:

{"message":"200\nGET /_security/_authenticate","trace":{"id":"6757659c7a30687eb7f31911612e184a"}}
{"message":"404\nGET /_security/role/logstash_read_user", "trace":{"id":"6757659c7a30687eb7f31911612e184a"}}
{"message":"200\nPUT /_security/role/logstash_read_user\n{\"cluster\":[\"manage_logstash_pipelines\"],\"indices\":[],\"run_as\":[],\"applications\":[]}", "trace":{"id":"6757659c7a30687eb7f31911612e184a"}}
{"path":"/api/security/role/logstash_read_user","query":""},"trace":{"id":"6757659c7a30687eb7f31911612e184a"},"message":"PUT /api/security/role/logstash_read_user 204 95ms"}

Note that the current implementation works for automatic instrumentation. If a plugin creates a custom transaction in a route handler manually, it must provide parents' trace.id to support Distributed Tracing.

const transaction = apmAgent.startTransaction('my-transaction', { childOf: apmAgent.currentTransaction });
// or
const span = apmAgent.startSpan('my-span', { childOf: apmAgent.currentTransaction });

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 67ab3d0
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💚 Build #8277 succeeded ddd43c1
• 💔 Build #8268 failed de5c783
• 💔 Build #7963 failed d916123
• 💔 Build #7942 failed fccd9e7
• 💔 Build #7809 failed fccd9e7
• 💔 Build #7767 failed 8567e97

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[TinaHeiligers]

It's a workaround for now and we'll need to keep checking on the apm issue status.
Core review only,
LGTM