Track SQL queries that use prepared statements

Nobody has claimed this yet.

If profiling of SQL queries is enabled we could also track SQL queries and average time it took to execute them. The information is written to `log_profiling` under circumstances anyway. We'd just need a way to figure out which ones were already tracked and to make sure to not send queries that contain any private information (only queries that use bind parameters). We could check if there's a use of `?` but still it could be the case that it is a mix of bound parameters and concatenated values...

It is not important but it would be kinda nice to see which queries are executed how often, how fast were they executed and especially to see a history of it.

Of course ideally there are monitoring tools used for such cases

Start by locating the existing `log_profiling` path mentioned in the issue and inspect how profiling information is currently written. Determine how prepared statements and bind parameters can be identified without sending private values. Done means safely recording query frequency, execution time, and history only for qualifying queries, with tests covering the privacy constraint.

Written by the indexing model from the issue text.