Use Ubuntu 20.04 for Release Builds

[mattlord]

Description

This moves the release package build CI workflow to Ubuntu 20.04, which is the oldest supported Linux distro available on GitHub hosted runners today.

This will get us back to what we were using with v14 and the vtorc binary — which links in the native sqlite C library via cgo — will be usable on a larger set of Linux distros. For additional details see: #12185

We may want to investigate additional options at some point, even going so far as attempting to statically link glibc in sqlite and using that resulting archive rather than shared object, but this PR gets us back to where we were and improves the situation significantly.

Related Issue(s)

• Helps with: Releases: VTOrc Unusable on Many Linux Platforms #12185

Checklist

• "Backport to:" labels have been added if this change should be back-ported
• Tests are not required
• Documentation 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.
• 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 test is added or modified, there should be a documentation on top of the test to explain what the expected behavior is what the test does.

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.

[GuptaManan100]

Thank-you!

[rohit-nayak-ps]

lgtm

[vitess-bot]

I was unable to backport this Pull Request to the following branches: release-15.0.