cli, kv: evaluate latency impact of pre-checks on decommission. #98246
Description
In #96100, we introduced decommission pre-checks in order to evaluate the decommission readiness of a node upon running cockroach node decommission. As this feature is new and enabled by default on all invocations of node decommission, it would be good to evaluate the impact of the checks on the latency of running node decommission using observability tooling such as logs and/or metrics. This was raised as a potential issue in a pre-mortem for the upcoming release cycle.
Jira issue: CRDB-25150