Vitess tester workflow

[GuptaManan100]

Description

This PR is a proof of concept on how to use the vitess-tester for e2e testing in Vitess. It adds a new workflow that runs the vitess-tester. The framework for generating more such workflows has also been added.

Some of the tests from go/test/endtoend/vtgate/queries/derived package have been copied over there too.
We have added tpch and tpcc tests as e2e tests running using the vitess tester.

Test summary are working with the changes, and the workflow fails correctly with an error

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 68.56%. Comparing base (adef4c2) to head (fbf2cd2).
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16127      +/-   ##
==========================================
- Coverage   68.57%   68.56%   -0.02%     
==========================================
  Files        1544     1544              
  Lines      197863   197895      +32     
==========================================
+ Hits       135687   135688       +1     
- Misses      62176    62207      +31     

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

[harshit-gangal]

do these have to be in different packages?

[GuptaManan100]

They share some tables with the same table name but different schemas. I was previously running them in the same package by changing some table names, but now I'm doing them as separate packages.

[harshit-gangal]

how does this template help? where can we configure and add more test paths?

[GuptaManan100]

You just create a new directory in the vitess_tester directory and put the .test files there and a vschema.json if there is one.
Once the workflow becomes too big and we want to create a new one, then we can create a new directory and put a new workflow in ci_workflow_gen.go to create a new one using the same template.