Add TransactionsProcessed metric to track transactions at VTGate

[harshit-gangal]

Description

This PR introduces a new counter metric TransactionsProcessed to VTGate to track the number of transactions processed, categorized by:

• Shard distribution: single or cross
• Transaction type: read only or read write

Related Issue(s)

• Closes RFC: New vtgate Metrics #17585

Checklist

• 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

[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

Attention: Patch coverage is 87.50000% with 5 lines in your changes missing coverage. Please review.

Project coverage is 67.54%. Comparing base (9e734f8) to head (7d4cfd7).
Report is 29 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtgate/tx_conn.go	87.50%	5 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #18171   +/-   ##
=======================================
  Coverage   67.53%   67.54%           
=======================================
  Files        1601     1601           
  Lines      261484   261509   +25     
=======================================
+ Hits       176592   176628   +36     
+ Misses      84892    84881   -11     

☔ 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.

[github-actions]

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

• Push additional commits to the associated branch.
• Remove the stale label.
• Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

[frouioui]

These should probably be constants