BUG: Audit API JWT failure is logged as an unhandled exception

**Describe the Bug**

A `POST /api/audit` request fails JWT authentication with a 401 response and is emitted by `AppAllExceptionsFilter` as an unhandled error.

**Expected Behaviour**

- Authentication failures are handled as expected client responses and do not generate misleading unhandled-exception error logs.
- Ensure the web application will no longer call the endpoint if the token is not present or no longer valid; for instance, ensure it is not expired, which is a possible assumption that may be causing most of the issues.
- For this endpoint, if the token is not validated, do not generate an unhandled exception that would lead to the `AppAllExceptionsFilter` log.

**Actual Behaviour**

The API returns 401 and records `UnauthorizedException: Unauthorized` as an unhandled exception.

**Log**

```text
[Nest] 18 - 09/04/2026, 3:40:17 PM LOG [AccessLoggerMiddleware] Request - POST /api/audit From [redacted] | User GUID: [redacted] | User Agent: Chrome 116 on macOS
[Nest] 18 - 09/04/2026, 3:40:17 PM ERROR [AppAllExceptionsFilter] Unhandled exception, request path: /api/audit
{
"stack": "UnauthorizedException: Unauthorized\n at JwtAuthGuard.handleRequest (/app/node_modules/@nestjs/passport/dist/auth.guard.js:60:30)",
"response": { "message": "Unauthorized" },
"status": 401,
"message": "Unauthorized",
"name": "UnauthorizedException"
}
```