Add support for querylog-time-threshold duration flag for query logging

[HenryCaiHaiying]

Description

Currently vtgate/vttable query log supports flag --querylog-row-threshold uint to emit query log when the row count is over a threshold. This PR adds the flag --querylog-time-threshold time.duration to emit query log when the query execution time over the time threshold.

On MySQL side, we have slow-query-log which emits slow query based on either execution time or affected rows, it would be good vtgate/tablet can issue the query log using the same criteria so we can correlate the log from both vitess and mysql sides.

The implementation pretty much followed the code path for querylog-row-threshold, the new flag querylog-time-threshold takes in a duration argument.  The duration can be expressed in a form recognized by time.ParseDuration (e.g. 300ms, 100ns).

Unit tests are added to cover the new querylog-time-threshold

The fix can be back ported to releases v21 and v22 since those releases have the same issue and can be benefited from the same fix, the back port should be straightforward.

Related Issue(s)

• Fixes Feature Request: add support for query_log_time_threshold for query logging #18456

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

None

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.50%. Comparing base (22f9190) to head (c34127f).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #18520   +/-   ##
=======================================
  Coverage   67.50%   67.50%           
=======================================
  Files        1607     1607           
  Lines      263046   263093   +47     
=======================================
+ Hits       177561   177605   +44     
- Misses      85485    85488    +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dbussink]

The fix can be back ported to releases v21 and v22 since those releases have the same issue and can be benefited from the same fix, the back port should be straightforward.

As this is a new enhancement and not a bug fix, it won't be back ported.