Implement support for generated and user provided Trace Id

Is your feature request related to a problem? Please describe.
Diagnosing issues across systems can be quite difficult, allowing a user request to provide a UUID as a Trace-ID will allow various applications and usages to Better gather logs.

Additionally, while the incident identifier is useful for getting the spot of error, a trace id would make it easier to assosciate all log messages from the start to that point.

Describe the solution you'd like

• If not provided Generate a Trace-ID to use in the current request, including passing to threads.
• Take the Trace Id from the X-Trace-ID header and use it for the session, if valid.

Describe alternatives you've considered
Keep guessing which messages are for who?

Additional context

• Slf4j provides a ThreadLocal "MappedDiagnosticContext", Flogger provides instances of a ScopedContext. I'm not sure how to go about this for Flogger, at least with Javalin, we will likely need to take care to put it in the Javalin Context object and use it when appropriate.

• OpenDCS recently did this using SLF4j https://github.com/opendcs/opendcs/pull/1845

Start by tracing how Javalin handles the request Context and how Flogger logging context is applied, using the X-Trace-ID header and the issue's ScopedContext discussion as the starting points. Done means a valid supplied ID is used for the session, otherwise an ID is generated and propagated to request threads and associated log messages.