UX: codeql database analyze should display timestamps

When executing the `codeql database analyze [] -- ` the CodeQL runs the queries from the given query suite by first loading them, compiling a query plan and then evaluating the queries.

The evaluation of certain queries can have a very pessimistic execution time and in some cases, when a project (database) is huge or/and for complex or poorly written queries, the execution of a given query may never finish.

It would be awesome if the CodeQL CLI would show timestamps by default so that one could see when the `Starting evaluation of ` actually started to see how long it is being executed already, to decide whether to stop it etc.

Please see also: #17930 and #17929.

The issue names no source files, tests, or entry points. Start by locating the implementation of `codeql database analyze` and the existing `Starting evaluation of ` output, then identify the relevant CLI tests; done means the command displays timestamps by default so evaluation duration can be judged.

Written by the indexing model from the issue text.