FEATURE: show time spent in CatchUpHooks (during CLI maintenance commands)

[skurfuerst]

Is there an existing issue for this topic?

• I have searched the existing issues

Description

During #5579, we found an issue ( neos/content-repository-search#58 ) which was a bit hard to debug.

So when executing a Command, it would be awesome if:

• we log the total time of a catchup
• we know how long each catchup hook took
• this is printed to CLI; and optionally also (later) logged with some metrics

Possible Solution

No response

[bwaidelich]

IIRC we currently route all catchups via the DelegatingCatchUpHook – maybe we can add some options to that one to enable tracing – or (probably cleaner) allow it to be replaced with some TracingCatchUpHook via Objects.yaml.

Slightly related: We should think about ways to trigger these hooks/projections asynchronously where it is possible