Collecting event logs

## Background
The Cloud Pipeline platform shall collect logs from all events that occur in the system - to trace back actions for bug fixes or identify incorrect user actions.

## Approach
We need to check which logs are currently collected and implement the gathering of "missing" events logs that haven't been collecting yet.
All logs shall be collecting automatically.

### Events
Events that shall be logged:
1. Create/update/delete operations (including permissions operations) over the following objects:
- library folder (including clone/lock operations)
- pipeline (including unregister/"register existing" operations)
- detach configuration
- object storage (including unregister/"register existing" operations)
- FS storage (including unregister/"register existing" operation)
- metadata
- project
- tool (including instance management)
- tool group
- registry
- object issues
- object attributes (tags)
2. Create/update/delete operations over the following system objects:
- user
- user group
- role
- system events (notifications)
- email notifications
- system-level preferences
- Cloud Regions preferences
3. Full run history regardless where the run was launched (pipeline, detach configuration, metadata, tool) including the following operations:
- lifecycle management (launch/rerun, pause, resume, stop, terminate operations, etc. including failures)
- user's activity within an interactive session (console/SSH session/FS browser)
- "sharing run" operation
4. Cluster state changes (nodes lifecycle)
5. Global search query history
6. System authorization (login/logout operations)
7. System exceptions, warnings, errors, failures

### Log information
Each event record shall contain at least the following info:
- Datetime
- User ID (if applicable)
- Event type
- Event description
- Object type (entity) (if applicable)
- Object ID and name (if applicable)