Track shard session affecting change inside the transaction

[harshit-gangal]

Description

This PR adds tracking on per shard transaction on VTGate Session to know if DMLs caused any modification in the underlying database.

This will be used to restrict the participants of cross shard transactions ignoring non-modified shards from the list.
As this is part of VTGate Session, it cannot be used in same release as it could potentially break VTGate upgrade

Related Issue(s)

• RFC: Atomic Distributed Transactions #16245

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

[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 96.29630% with 4 lines in your changes missing coverage. Please review.

Project coverage is 67.41%. Comparing base (216fd70) to head (15ec122).
Report is 10 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtgate/safe_session.go	95.45%	3 Missing ⚠️
go/vt/vtgate/scatter_conn.go	97.61%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17266      +/-   ##
==========================================
+ Coverage   67.39%   67.41%   +0.02%     
==========================================
  Files        1570     1573       +3     
  Lines      252917   253132     +215     
==========================================
+ Hits       170446   170657     +211     
- Misses      82471    82475       +4     

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles