Allow users to specify a subset of fingerprints to track statistics for

This issue tracks capturing statements and transactions fingerprints for the top N fingerprints. N is a configurable setting and TOP is based on total latency (execution count * latency). This will enable a longer and flexible data retention period.

This issue is addressing proactive observability user flows where developers and operators would typically only care for a subset of their workload to track over time. E.g., Track the top N fingerprints taking up the majority of my database's time.

Jira issue: CRDB-24299