[Reputation Oracle] Revision/Refactoring

[Dzeranov]

Description
Need to do a revision of the Reputation Oracle. This is complex and ongoing process. All the necessary actions will be described below.

Action points

• [Reputation Oracle] Refactor error handling #2928
• [Reputation Oracle] Align response codes with best practices #3064
• [Reputation Oracle] Logging system #3065
• [Reputation Oracle] Revisit business logic #3084
• Revisit snake case transformers (keys return in camelcase in validation errors)
• Revisit Github Actions: make sure jobs names are clear and necessary caching (PR)
• Avoid loading the full user from DB for every request when doing auth (PR)
• Get rid of HUMAN App in DB (PR)
• Setup up CASCADE on DB relations for proper deletions (PR)
• Split user & operator to different tables (icebox: no viable profit for performance, but it's heavy lifting)
• Change primary ids of entities to be uuid instead of SERIAL (icebox: we have space for maneuver here; if we are close to the limits - change column type to bigint and work on it; tokens table is number 1 candidate)
• Add TTL on refresh tokens in DB (PR)