Add Flag to disable Connection Logs & Audit Logs

Problem

High‑volume environments are seeing:

- Extremely large numbers of audit log and connection log entries, especially:
- Connection logs generated by certain IDE workflows (e.g., IntelliJ Remote Dev health checks).
- Database growth dominated by these logs (tens of thousands of entries per month, tens of GB of storage).
- SRE/DBA time consumed on cleanup (e.g., manual table purges, tape‑backup‑based restores)

In some cases, UIs become effectively unusable because of the amount of data being ingested.

Today, customers have no way to shut off or sharply limit these logs at the source. They are forced into reactive DB maintenance and custom cleanup jobs.

Desired Outcome

Admins should be able to:

- Disable or aggressively limit audit log and connection log ingestion at a configuration level.
- Scope controls by:
- Log type (audit vs. connection).
- Endpoint/host class (e.g., dev/internal hosts vs. production platform traffic).
- Severity or status codes (e.g., ignore 5xx from certain internal paths).
- Ensure that disabling or throttling logs:
- Reduces DB growth.
- Prevents UI and API endpoints for logs from becoming a reliability risk.
- Keeps on‑call alerts focused on real platform health issues, not noisy user/IDE behavior.