sql: fix performance when disabling sql.metrics.statement_details

[j82w]

There is a performance regression when disabling
sql.metrics.statement_details.enabled. It will see that every execution is the first time the query was executed so it will enabled execution stats collection for all executions. This is a bug caused by always collecting the execution stats of the first time a statement is executed in #89418.

Fixes: #106811

Release note (bug fix): Fixes a bug causing performance regression when disabling sql.metrics.statement_details.enabled which caused execution stats to be
collected for all queries instead of the default one percent.

[cockroach-teamcity]

This change is 

[maryliag]

this should also be backported to 22.2

Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @j82w)

[maryliag]

looks like something must be wrong with the code because the new test is failing

Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @j82w)

[j82w]

The test failure is fixed now. The execution stats are still enabled 1% of the time which caused it to be flaky. I changed the logic so all 4 executions had to have executions stats collected for it to fail.

[j82w]

bors r+

[craig]

Build succeeded:

• Bazel Essential CI (Cockroach)

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating merge commit from 716f6a9 to blathers/backport-release-22.2-109785: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 22.2.x failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}