Foreign Key Fuzzer Benchmark

[GuptaManan100]

Description

This PR adds foreign key benchmarking that uses the fuzzer to generate its set of queries. It runs the queries against MySQL, a Vitess-managed keyspace, and a Vitess-unmanaged keyspace. This allows us to know the difference between the performance of Vitess managed and unmanaged modes.

Benchmark results look like the following -

goos: darwin
goarch: arm64
pkg: vitess.io/vitess/go/test/endtoend/vtgate/foreignkey
BenchmarkFkFuzz
BenchmarkFkFuzz/MySQL
BenchmarkFkFuzz/MySQL-10         	1000000000	         0.1547 ns/op
BenchmarkFkFuzz/Vitess_Managed_Foreign_Keys
BenchmarkFkFuzz/Vitess_Managed_Foreign_Keys-10         	1000000000	         0.4586 ns/op
BenchmarkFkFuzz/Vitess_Unmanaged_Foreign_Keys
BenchmarkFkFuzz/Vitess_Unmanaged_Foreign_Keys-10       	1000000000	         0.3459 ns/op
PASS

Related Issue(s)

• RFC: Foreign Key Support in Vitess #12967

Checklist

• "Backport to:" labels have been added if this change should be back-ported
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on the 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.

[harshit-gangal]

Can you add benchmark details to the PR description or as a comment?

[harshit-gangal]

Can you also add the benchstat numbers to know how it fairs?