Omni audit logs future ideas

[DmitriyMV]

Split from #37

Future ideas

Preview Give feedback

1. Allow user to specify the retention policy
2. Allow user to speciby the begin and end dates for getting logger
3. Add support for MachineClass resources.
4. Resource deletion should also print associated labels.
5. Log when user downloads talosconfig.
6. Log when user downloads kubeconfig.
7. Maybe drop GET requests from logging k8s access.
8. Compress audit logs after rotation
9. Allow user to forward audit logs to external log receiver (splunk, syslogd, etc)
10. Allow user to see/search audit records directly in Omni web UI

[steverfrancis]

I dont think there is any use case for allowing the user to specify the audit retention policy.
As a user, I will just want as much retention as possible.

Rather, I think WE need to specify an audit policy: retention of 30 days events, or X number of events, which ever is smaller.
That way if someone hammers something that causes logs, we aren't on the hook to provide an infinite amount of storage in order to meet 30 days retention.