🐛 Inject kcp-start-informers logger into correct hook context

[embik]

Summary

I've observed log lines like the one below for quite a while:

{"ts":1715849616335.2378,"caller":"replication/replication_reconcile.go:200","msg":"Updating object in global cache","component":"kcp","postStartHook":"kcp-start-informers","postStartHook":"kcp-start-controllers","reconciler":"kcp-replication-controller","key":"v1.clusterroles.rbac.authorization.k8s.io::root|system:kcp:universal-workspacetype-use","reconcilerKey":"root|system:kcp:universal-workspacetype-use","kind":"ClusterRole","namespace":"","name":"system:kcp:universal-workspacetype-use","v":2}

Note the double entry "postStartHook":"kcp-start-informers","postStartHook":"kcp-start-controllers".

Turns out that in the kcp-start-informers post start hook the logger gets injected into ctx. That's however not the context of the hook, it's the main context used by the whole (s *Server) Run method! This PR creates a new hookCtx that is explicitly instantiated within the hook and is subsequently passed to all informers and the server bootstrap code.

Note this is relatively low priority and I don't want it to block #3132.

Related issue(s)

Fixes #

Release Notes

Fix `postStartHook` being present two times on log lines

[kcp-ci-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[embik]

/cc @mjudeikis @xrstf

[xrstf]

/approve

[kcp-ci-bot]

LGTM label has been added.

Git tree hash: 905c156049115f6b32ecd76717bb1179533b238c

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xrstf

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [xrstf]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment