fix distributed transactions disruptions test with move table

[harshit-gangal]

Description

Fuzzer test and Stress test were using common state which sometimes leave twopc_fuzzer_update table on 2 keyspaces.
It causes an ambiguous error on running move tables disruption on the stress test after fuzz test have completed.

The PR split these into two different packages so that they do not interact with each other.

Related Issue(s)

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

All modified and coverable lines are covered by tests ✅

Project coverage is 68.93%. Comparing base (d9e59b6) to head (a8e8fee).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16765      +/-   ##
==========================================
- Coverage   68.94%   68.93%   -0.01%     
==========================================
  Files        1565     1565              
  Lines      201764   201764              
==========================================
- Hits       139112   139095      -17     
- Misses      62652    62669      +17     

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

[shlomi-noach]

Personal preference to always use context.WithTimeout and then cehck for <- ctx.Done(). This would also do the right thing for mysqlConnec(ctx, ...).

[harshit-gangal]

for this PR, I will leave it as-is. As it is concerned with resolving flaky test issues.