feat: audit log steel thread

[superlinkx]

Description

Steel Thread for Audit Logging

Motivation and Context

We needed to change our approach to audit logging. This contains the first 4 DB methods to get audit logging to use as reference for our other priority 1 audit enabled methods.

How Has This Been Tested?

Existing tests were modified as necessary, but generally kept as close to the originals as possible. Passing tests means there's good confidence that these changes are correct, but additional testing should be completed before the main populate-audit-log-fields gets merged.

Types of changes

• Chore (a change that does not modify the application functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• Documentation updates are needed, and have been made accordingly.
• I have added and/or updated tests to cover my changes.
• All new and existing tests passed.
• My changes include a database migration.