[release-18.0] planbuilder bugfix: expose columns through derived tables (#14501)

[vitess-bot]

Description

This is a backport of #14501

[vitess-bot]

Hello @systay, there are conflicts in this backport.

Please address them in order to merge this Pull Request. You can execute the snippet below to reset your branch and resolve the conflict manually.

Make sure you replace origin by the name of the vitessio/vitess remote

git fetch --all
gh pr checkout 14504 -R vitessio/vitess
git reset --hard origin/release-18.0
git cherry-pick -m 1 817c24e9428d832ae61527c79182cc1a7a9b6672

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

[deepthi]

@frouioui tests are failing with

2023/11/11 17:02:09 Pulling vitess/bootstrap:22.2-mysql57...
2023/11/11 17:02:16 Can't pull image vitess/bootstrap:22.2-mysql57: exit status 1

which is weird because I can see that image in docker hub https://hub.docker.com/layers/vitess/bootstrap/22.2-mysql57/images/sha256-d1a904b2d287bf8845edc19f53500e077c0102f5a4e8789f5a4bd27d38d22fb8?context=repo

[deepthi]

@systay are we not losing coverage by removing this test? And if we are not, we should pick it into all active branches, because these tests have been flaky everywhere.