fix: handle WebSocket connections in audit log exception handlers (M2-11023)

[sricharan-varanasi]

• Tests for the changes have been added
• Related documentation has been added / updated
• For new features, QA automation engineers have been tagged
• OSS packages added to Curious open source credit page

📝 Description

🔗 Jira Ticket M2-11023

Fixes a crash in the user:session:invalid audit log handlers when authentication
fails on the /ws/alerts WebSocket.

http_audit_fields read the HTTP-only request.method, which a WebSocket does not
have - so an expired/invalid token on the alerts WebSocket raised AttributeError
inside the exception handler. The audit event was never recorded and the client's 401
was never sent.

Changes include:

• http_audit_fields now accepts any HTTPConnection and omits http.request.method
  for WebSocket connections (the audit model already allows it to be null).
• Widened the affected exception handlers to HTTPConnection so the types match what
  they actually receive at runtime.
• Added a regression test covering the WebSocket auth-failure path.

✏️ Notes

No API/schema changes.

[divbzero]

Looks good. Thank you @sricharan-varanasi.