Move CI workflow to use latest community version of mysql 8.0

[rsajwani]

Signed-off-by: Rameez Sajwani rameezwazirali@hotmail.com

Description

This PR is build on top of #11153.
We are moving end to end and unit test to use latest version of MySql 8.0 instead of using percona. The reason for this is that Percona is still at 8.0.29, this doesn't allow our code base to test against the latest version of mysql.

Unit test are already on mysql community version but we are upgrading to higher apt-config version

Related Issue(s)

#11511

Checklist

• "Backport me!" label has been added if this change should be backported
• Tests were added or are not required
• 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.
• If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.

If a new flag is being introduced:

• Is it really necessary to add this flag?
• Flag names should be clear and intuitive (as far as possible)
• Help text should be descriptive.
• Flag names should use dashes (-) as word separators rather than underscores (_).

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow should be required, the maintainer team should be notified.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should include a link to an issue that describes the bug.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• vtctl command output order should be stable and awk-able.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from VTop, if used there.

[frouioui]

Left a few comments. We should also update the PR's description to describe this change and ideally link to an issue if there is one.

[frouioui]

By the way, do we need to forwardport this to main considering the work that has been merged in this PR: #11153?

[deepthi]

By the way, do we need to forwardport this to main considering the work that has been merged in this PR: #11153?

This is why we need a better PR description.
#11153 is already present in release-15.0. On top of that this PR is changing the MySQL version we use from Percona to community version.
The reason for this is that Percona is still at 8.0.29, so the new backup code we wrote for changes in 8.0.30 is not being exercised.
Unit tests are already using community version. This PR changes endtoend tests to do the same (except xtrabackup tests).

[rsajwani]

FYI, Cluster (26)
was failing ..I tried to debug but doesn't seems it is because of my change. Running it manually then passed... So i am attributing it to flakiness...

[frouioui]

Looks good to me now

[vitess-bot]

I was unable to forwardport this Pull Request to the following branches: main.

[deepthi]

@frouioui @GuptaManan100 can you review the upgrade/downgrade tests to see what versions we use there, and whether any changes are needed?

[frouioui]

@deepthi, this issue should be addressed as soon as we merge #11509