System services for evitaLab

[lukashornych]

We will need several internal APIs for evitaLab management tooling. Ideally, we would want to use gRPC with gRPC-web for it.

• API for fetching evita configuration
• API for job listing with status and polling
• executing unsafe query

API for backups

• listing backups for catalogs
• recording
• downloading
• restoring from evitaDB's stored file
• importing from external file

API for JFR

• listing recordings
• downloading
• recording
• fetching list of available JFR events

API for mutations in WAL log

• listing, filtering, sorting

API for query recordings

• listing
• downloading
• replaying
• filtering
• recording

[lukashornych]

We will also need to support unsafe mode for evitaQL when querying data. It could be just a parameter in input object when querying data. evitaLab would use by default unsafe mode. There could than be a switch in evitaQL console to switch to safe mode for debugging or something.

There will be new methods in gRPC services:

• queryUnsafe
• queryOneUnsafe
• queryListUnsafe

We want to explicitly distinguish, so the developer using it doesn't accidentally use unsafe mode.