Capture the physical execution plans per fingerprint and plan gist

Today we automatically capture all logical plans for each fingerprint. Users lack visibility into execution statistics and information on which nodes the statement was executed on. This issue tracks providing a process to capture physical execution plan per fingerprint per plan. We should consider approaches that will allow us to collect as much execution plans as possible without impact service latency.

Related issues:

- Support issue: https://github.com/cockroachlabs/support/issues/2079
- Other feedback issues: https://github.com/cockroachdb/cockroach/issues/92415

Jira issue: CRDB-24891