Release v22.136.3

Fixed

• Work that starts during an HTTP request and runs after the request has ended no longer sees that request as current. Examples are a Chronicle reactor dispatched from an append made in the request, a background task, or a timer. Reading the current user from such work used to throw ObjectDisposedException ("IFeatureCollection has been disposed"), which failed every event the reactor appended. It now resolves the identity as it does outside a request. (#3501)