Extract request id handling to dedicated class so it can be injected without DB dependency

[nickvergessen]

Logs before (with query_log_file):

SELECT * FROM `oc_appconfig`
SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
SET SESSION AUTOCOMMIT=1
SELECT `class`, `entity`, CAST(`events` AS CHAR) AS `events` FROM `oc_flow_operations` WHERE `events` <> :dcValue1 GROUP BY `class`, `entity`, CAST(`events` AS CHAR)

Logs after (with query_log_file and query_log_file_requestid === yes)

jjI3eJAK1Ljz1OptLtpG	SELECT * FROM `oc_appconfig`
jjI3eJAK1Ljz1OptLtpG	SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
jjI3eJAK1Ljz1OptLtpG	SET SESSION AUTOCOMMIT=1
jjI3eJAK1Ljz1OptLtpG	SELECT `class`, `entity`, CAST(`events` AS CHAR) AS `events` FROM `oc_flow_operations` WHERE `events` <> :dcValue1 GROUP BY `class`, `entity`, CAST(`events` AS CHAR)

Required for more in depth debugging on parallel requests

[CarlSchwan]

Tests needs to be adapted, but other than a few small nitpicks this looks fine to me.

In some ways, this feels a bit like duplicated work with #30823 since the requests are also stored with the requested (and arguments + execution time) there :/

We might want to discuss how we want to move forward since there is also OCP\Diagnostics too that also logs queries and having 3 DB requests loggers is maybe a bit too much

[nickvergessen]

In some ways, this feels a bit like duplicated work with #30823 since the requests are also stored with the requested (and arguments + execution time) there :/

Happy to talk about it. The problem is the profiler only helps in an isolated testing case. There is no way to e.g. monitor the full company call with it.

We might want to discuss how we want to move forward since there is also OCP\Diagnostics too that also logs queries and having 3 DB requests loggers is maybe a bit too much

That's also right. I need to checkout the Diagnostics stuff again what it does and can do.