Implement logging for user actions

[jayjaybunce]

🗣 Description

• Adds logging to several backend routes via Homebrew Logger class to allow traceback of user activities: adding user to an organization, inviting a user, removing a user or updating a user.

💭 Motivation and context

Resolves CRASM-569

🧪 Testing

1. Create temporary table for the log record
   sql CREATE TABLE public.log ( "id" SERIAL PRIMARY KEY, "payload" json NOT NULL, "createdAt" timestamptz NOT NULL DEFAULT now(), "eventType" varchar NOT NULL, "result" varchar NOT NULL );
2. Invite a user and assign them to an organization
3. Deny a user's request
4. Approve a user's request
5. View User Logs by going to Admin Tools => Select the User Logs tab

Filters implemented:

1. Result => Either 'success' or 'fail'
2. Payload => JSON object you can search with this format: createdUserPayload.id: a23das12312n-asda912-asd
3. Timestamp
4. EventType

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All future TODOs are captured in issues, which are referenced
  in code comments.
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated
  to reflect the changes in this PR.
• Tests have been added and/or modified to cover the changes in this PR.
• All new and existing tests pass.

✅ Pre-merge checklist

• Revert dependencies to default branches.
• Finalize version.

✅ Post-merge checklist

• Create a release.

[ameliav]

Works for me after adding the log table :)