Continue building base/k8s when tag version is below v20

[frouioui]

Description

Fix various bug found after merging #15620:

• We still want to build base and k8s on older tags (<v20)
• Some files were not copied properly between the bootstrap image and the lite image

Validated in CI: https://github.com/vitessio/vitess/actions/runs/8547164210/job/23418901908?pr=15638

[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.

[frouioui]

This is a pure copy of what we used to have before #15620, only the workflow name and the tags-ignore field on lines 4 and 5 changed.

[frouioui]

Same here

[deepthi]

I assume that the reason you are having to do this is because our releases always use tooling from main? Otherwise, things should keep working on release branches, no? We should plan to fix this properly.

[frouioui]

I assume that the reason you are having to do this is because our releases always use tooling from main? Otherwise, things should keep working on release branches, no?

IIRC when pushing a new tag, GitHub Actions will use the workflows found on the main branch. Not the workflows found on the tag's commit.