[FEATURE] Audit service should chain events

[s-vitaliy]

Description

Today audit service emits the events one-by-one which can overflow the logging infrastrucutre and make logs harder to read.

Possible solution

Instead of it we need a something like a "chaining" solution where audit events travel alongside the request and emitted only when the final decision (allow/disallow access) is made.

Alternatives

(?)

Context

Can be done with #70