Indicate whether the cause of a 'timestamp push' was due to the 'closed timestamp'

Transactions can have their timestamps pushed due to hitting the [closed timestamp duration threshold](https://www.cockroachlabs.com/docs/v22.2/architecture/transaction-layer#closed-timestamps) and subsequently failing with a [retry error](https://www.cockroachlabs.com/docs/stable/transaction-retry-error-reference.html#retry_serializable) (e.g., RETRY_SERIALIZABLE and RETRY_COMMIT_DEADLINE_EXCEEDED).

For these scenarios, we should provide information to indicate that the error originally stemmed from hitting the "closed timestamp". This information could be surfaced in the error message allowing client downstream systems (e.g., console) to consume this information and providing more prescriptive troubleshooting guidance to end users.

This will allow users to focus on reducing the "size" (latency) of their transactions and in some scenarios, increase the closed timestamp duration threshold.

Jira issue: CRDB-22611