Basic audit trails via logging

[ammar92]

Changes

This PR implements some more audit trails via logging:

• Adding, creating and deleting objects
• Plugins
  • Change plugin state
  • Update plugin settings
• Raw data has been uploaded
• Login, logout and failed logins
• Organization creation and deletion

Most of the other logging related to models have been implemented in #3314 and merged into this branch.

Also implemented basic event codes for specific ORM record trails. This is a very basic implementation to get things started. I also considered using a tuple for the event codes (an element for each CRUDE action), but since there's probably still room for improvement and development around the audit trails I used a dict for now for flexibility.

Ideally we'd use more descriptive codes (using alphanumerics) when possible. In both cases, whether we use alphanumeric or numeric codes, we should work towards automatically labeling them as much as possible.

Issue link

Partially closes #3043

QA notes

You should see more logging on certain actions, such as creating an object or enabling a plugin. On certain model changes (such as an organization or organization tags), you should also see an event_code variable in the log record.

---

Code Checklist

• All the commits in this PR are properly PGP-signed and verified.
• This PR only contains functionality relevant to the issue.
• I have written unit tests for the changes or fixes I made.
• I have checked the documentation and made changes where necessary.
• I have performed a self-review of my code and refactored it to the best of my abilities.

• Tickets have been created for newly discovered issues.
• For any non-trivial functionality, I have added integration and/or end-to-end tests.
• I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
• I have included comments in the code to elaborate on what is not self-evident from the code itself, including references to issues and discussions online, or implicit behavior of an interface.

---

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.

---

Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.

[stephanie0x00]

Checklist for QA:

• I have checked out this branch, and successfully ran a fresh make reset.
• I confirmed that there are no unintended functional regressions in this branch:
  • I have managed to pass the onboarding flow
  • Objects and Findings are created properly
  • Tasks are created and completed properly
• I confirmed that the PR's advertised feature or hotfix works as intended.
• I checked the logs for errors and/or warnings and made issues where necessary

What works:

Looks good. I see various events in the logs. Not observing anything weird, like error messages. Onboarding works and boefjes can be started and complete.

What doesn't work:

n/a

Bug or feature?:

n/a