Make resources auditable

[Randoooom]

[Randoooom]

This feature is now on top of the todo list as it is required to actually provide a performant way to authorize queries without parent id's. Therefore, as already discussed in #166 we would want to create an index table containing all the relations from a specific resource.

This can be done by utilizing the audits, as every audit event may affect the index and therefore can be used to even construct the index itself.

Enterprise solution:

• utilize a MessageBroker for that, Fluvio to be specific (this would help us with Create wasm response interceptors for custom validation #55)
• create a new instance type, the indexer instance which maintains the index and creates the audit data
• all indexer listen with the same consumergroup to the audit topic
• all worker instances (the "normal" instances) listen with a unique consumergroup to the audit topic
• worker can now publish cache invalidations directly via the broker, allowing us to use the worker in memory as L1 and Skytable as L2 without encountering sync errors
• worker publish every mutation to the audit log
• indexer update the index depending on the log event (e.g create entries, modify them and even delete them)
• indexer also create the audit database containing recent versions of important resources allowing us to roll them back

Alternative
If the user does not want to use a broker we will offer a broker free solution with only 1 indexer instance. Now the worker instances will send grpc requests to the indexer in an async scheme (here basically oneshot).

Implementation details:

• worker use a seperate thread to publish events or to send grpc requests to the indexer
• worker batch events
• the indexer should be able to repair the index via a cronjob where the entire index gets validated