Add flow ids to logging

[surajkumar]

As a user I want to...

be able to assign a unique flow ID to log messages within my system.

So that...

I can know which log message relates to which component of my system.

Acceptance Criteria

WHEN a log message is created
THEN then I should be able to attach a flow id it

WHEN a log message with a flow id is created
THEN I should be able to identify which component that message related to
AND the flow ID should be configurable, allowing flexibility in its format and generation method.
AND the logging system should support efficient retrieval and filtering of log messages based on the assigned flow ID
AND the flow ID assignment should be consistent across all components of the system, ensuring seamless tracking and correlation of log messages

[SquidXTV]

So I am working on it and the implementation itself is quite easy, just some questions that need to be answered:

1. What kind of log4j2 pattern do we want to use for this?
2. How should we generate the ID?
3. Should everything have a flow ID? or just stuff the user actually interacts with? Like incoming/outgoing requests
4. Where should we place the log4j2.xml file? It is currently in the gateway module, but is being used across that. There might be a need to have different ones though, depending on the 3) question.

[SquidXTV]

Paused until #99