In 22.2, we primarily have insights surfaced at the statement level. We should make this the default so it's more discoverable.

In 23.1, once we have transaction-level insights, we can revert the behavior as the transaction is typically the entry point for end users when debugging a performance issue.

Jira issue: CRDB-22057