Implement fallback MDC implementation for JUL

[SylvainJuge]

Part of elastic/apm-agent-java#2492

Adds a fallback MDC implementation for JUL that can be used by the APM agent, usage within ECS logging will only read any key/values in the MDC, values will be populated by the APM agent.

---

Checklist

• adding at least some comments to explain that the agent might rely on the code structure (the agent should test for that too)
• how to properly size the custom MDC size and load factor ?

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-08-01T15:26:59.793+0000

• Duration: 7 min 33 sec

Test stats 🧪

Test	Results
Failed	0
Passed	245
Skipped	0
Total	245

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[felixbarny]

@eyalkoren correct me if I'm wrong but I think the idea was to not rely on the MDC from slf4j at all anymore. Instead remove MdcSupplier and add a MDC class with static methods similar to org.slf4j.MDC.

[eyalkoren]

@eyalkoren correct me if I'm wrong but I think the idea was to not rely on the MDC from slf4j at all anymore. Instead remove MdcSupplier and add a MDC class with static methods similar to org.slf4j.MDC.

Correct, that's the preferable option described in elastic/apm-agent-java#2492 (comment), and the less preferable alternative described is to rely on slf4j MDC

[eyalkoren]

AFAICT it should be thread-safe as long as we keep the usage as is, but I added a proposal for increasing the chances that it is kept safe in the future as well