This is the second PR for moving connection events out of the audit log.

This PR:

• Adds the/api/v2/connectionlogs endpoint
• Adds filtering forGetAuthorizedConnectionLogsOffset and thus the endpoint.
  There's quite a few, but I was aiming for feature parity with the audit log.
  1. organization:<id|name>
  2. workspace_owner:<username>
  3. username:<username>
     • Only includes web-based connection events (workspace apps, web port forwarding) as only those include user metadata.
  4. email:<email>
  5. started_after:<time>
  6. started_before:<time>
  7. closed_after:<time>
  8. workspace_id:<id>
  9. connection_id:<id>
     • If you have one snapshot of the connection log, and some sessions are ongoing in that snapshot, you could use this filter to check if they've been closed since.
  10. status:<connected|disconnected>
      • Ifconnected only sessions with a nullclose_time are returned, ifdisconnected, only those with a non-nullclose_time`.

Future PRs:

• Populatecount onConnectionLogResponse using a seperate query (to preemptively mitigate the issue described inAudit log slows to a crawl when nearing 1 million entries #17689)
• Implement a table in the Web UI for viewing connection logs.
• Write a query to move N entries from the audit logs table to the connection logs table, call it from dbpurge.
• Write documentation for the endpoint / feature