Use the provided user info sent to the audit endpoint to get which user is triggering an operation

[Steve-Mcl]

closes #4529

Description

If a string value is provided for the audit event user property, look it up and use that for logging operations against the user

Related Issue(s)

owner #4529
parent #4413

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Includes a DB migration? -> add the area:migration label

[Steve-Mcl]

[codecov]

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 78.04%. Comparing base (31e884b) to head (c7b7e03).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
forge/routes/logging/index.js	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4530      +/-   ##
==========================================
- Coverage   78.07%   78.04%   -0.03%     
==========================================
  Files         300      300              
  Lines       14285    14273      -12     
  Branches     3241     3240       -1     
==========================================
- Hits        11153    11140      -13     
- Misses       3132     3133       +1     

Flag	Coverage Δ
backend	78.04% <80.00%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.