VReplication: Enforce consistent order for table copies and diffs

[mattlord]

Description

There was no consistent order used for tables copied/replicated in VReplication and for table's diffed in VDiff. Here we enforce consistent ordering for these things and thus their related show command output so that output/behavior is deterministic and it's easier for users to compare progress on similar workflows (e.g. when doing shard level migrations across many shards).

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

[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: 4 lines in your changes are missing coverage. Please review.

Comparison is base (c189cf4) 70.62% compared to head (84a2ef2) 70.64%.
Report is 6 commits behind head on main.

Files	Patch %	Lines
.../vt/vttablet/tabletmanager/vreplication/vcopier.go	71.42%	2 Missing ⚠️
go/vt/vtctl/workflow/resharder.go	0.00%	1 Missing ⚠️
go/vt/vttablet/tabletmanager/vdiff/table_differ.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15152      +/-   ##
==========================================
+ Coverage   70.62%   70.64%   +0.01%     
==========================================
  Files        1377     1378       +1     
  Lines      182794   182823      +29     
==========================================
+ Hits       129102   129159      +57     
+ Misses      53692    53664      -28     

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

[rohit-nayak-ps]

Looks good!