feat: Log redaction, FIFO QOS for user vs API HTTP requests and http traffic accounting enrichment

[Zacgoose]

This pull request introduces detailed endpoint-level accounting and interactive user traffic tracking to the egress logging and metering system. It also adds configurable log redaction for sensitive information in logs and console output. The changes enhance observability, enable more granular reporting, and improve privacy controls.

Egress metering enhancements:

• Endpoint-level tracking is now included in all egress accounting: each response is attributed to its endpoint, and statistics are maintained per endpoint for both API clients and interactive users. [1] [2] [3] [4]
• Interactive (signed-in user) traffic is tracked and reported separately, never counting against the API client cap, with its own partition in the accounting system. [1] [2] [3] [4] [5]
• The egress ledger file format is migrated to version 3 to persist endpoint and interactive user breakdowns. [1] [2]

Log redaction improvements:

• Added configuration options to FileLoggingSettings for masking UPNs and customer domains in logs, with an allow list for readable domains and environment variable override. [1] [2]
• Integrated a redacting console logger that applies the same redaction logic to console output, ensuring sensitive information is masked unless explicitly disabled.

Other improvements:

• Log lines are revealed (unredacted) when read via LogBridge, ensuring authorized access sees the original data.
• Egress accounting now records the endpoint label for shed (429) requests, improving cap-hit diagnostics. [1] [2]

These changes provide more accurate and privacy-aware logging and metering, supporting better reporting and diagnostics for both API and interactive user traffic.