Add [request id] context to relevant proxy log entries

[geo2a]

Most [proxy] log entries are prefixed with [request ID]. The exception are are entries that are emitted in-between requests.

Before:

[proxy] Starting RPC server
[proxy] Processing request 0
[proxy] Starting execute request
[request 0][booster][execute][depth] 0 steps.
...
[proxy] Booster Aborted at Depth {getNat = 0}
[proxy] Simplifying booster state and falling back to Kore
[proxy] Simplifying execution state
...

After:

[proxy] Starting RPC server
[proxy] Processing request 0
[request 0][proxy] Starting execute request
[request 0][booster][execute][depth] 0 steps.
...
[request 0][proxy] Booster Aborted at Depth {getNat = 0}
[request 0][proxy] Simplifying booster state and falling back to Kore
[request 0][proxy] Simplifying execution state
...

[jberthold]

LGTM.
Only question is, are we now getting duplicated request <N> entries for the sections where koreRespond is working on the request?

[geo2a]

@jberthold I though we would, and removed the code that adds tre request id in Kore, but got the output with no request id for Kore 🙅 I think something in the logger setup requires us to explicitly add them in Kore.