Username does not always populate correctly in change logs when config writes occur

[jaredhendrickson13]

Describe the bug

In certain cases, a successful API call that results in a config write does not retain the authenticated username and will fallback to the default, (system).

To Reproduce
Steps to reproduce the behavior:

1. Do a fresh install of v2 on a fresh install of pfSense 2.7.2.
2. Before signing into the UI, make any API call that writes a change to the config.
3. Go to Diagnostics > Backup & Restore > Config History and see that the change did not retain the authenticated username

Expected behavior
All config writes performed via authenticated API calls should write the username who made the call.

pfSense Version & Package Version:

• pfSense Version: pfSense 2.7.2 (Likely affects Plus as well)
• Package Version: v2.0.1

Affected Endpoints:

Any that perform a config write.

Additional context

This only seems to occur if there are no active PHP sessions. After any user starts a session, the username appears in the change logs as expected.