DRAFT: Spike: Commands and audit event logs base set up

[Patrick Sweeting (psweeting1)]

What

Link to story

Describe what you did and why.

Checklist

Before you ask people to review this PR:

• Tests should be passing: ./gradlew test
• GitHub should not be reporting conflicts; you should have recently run git rebase main.
• Avoid mixing whitespace changes with code changes in the same commit. These make diffs harder to read and conflicts more likely.
• You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
• You should have checked that the commit messages say why the change was made.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.