CI: Temporarily skip flaky TestMoveTablesUnsharded

[rohit-nayak-ps]

Description

The unit test TestMoveTablesUnsharded is increasingly flaky. Works locally everytime and also on a separate PR where I only enabled the unit test workflows, it didn't fail a few times I ran them. However on most PRs it seems to fail at least one of the tests (usually the 84 test, though that might be a coincidence).

For now skipping the test until we fix the flakiness.

Related Issue(s)

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

[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 69.51%. Comparing base (e68bdd5) to head (c24a68f).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16812      +/-   ##
==========================================
- Coverage   69.53%   69.51%   -0.02%     
==========================================
  Files        1568     1568              
  Lines      202423   202423              
==========================================
- Hits       140747   140714      -33     
- Misses      61676    61709      +33     

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