Include Statement Fingerprint ID in Detailed Latency Metrics

Currently, when detailed latency metrics are enabled, we expose the statement fingerprint (i.e., the SQL text), but not the statement fingerprint ID. We've received feedback that this ID is crucial for correlating data across monitoring tools and the DB Console.

Without surfacing the ID in latency metrics, users can't easily match telemetry data from external tools to what's shown in the DB Console. This disconnect limits users' ability to troubleshoot and understand query performance end-to-end.

We should include the statement fingerprint ID in the detailed latency metrics payload as a separate label. This would:

- Improve observability and traceability.
- Help users bridge the gap between external monitoring tools and CockroachDB’s internal views.
- Enable more efficient debugging and performance tuning.

Jira issue: CRDB-51010