Properly unescape keyspace name in FindAllShardsInKeyspace

[mattlord]

Description

This is needed because the input to this function comes from e.g. the vschema, where a keyspace name that contains special characters such as a dash needs to be SQL escaped with backticks.

I think that we should backport this to v19 as that's when we started making heavier use of this function via #15047 (and #15117).

Related Issue(s)

• Fixes: Bug Report: Errors encountered with database/keyspace name that contains special chars #15766

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or 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.
• 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.40%. Comparing base (14b36d0) to head (e9521bc).
Report is 9 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #15765   +/-   ##
=======================================
  Coverage   68.39%   68.40%           
=======================================
  Files        1556     1556           
  Lines      195422   195425    +3     
=======================================
+ Hits       133666   133672    +6     
+ Misses      61756    61753    -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[GrahamCampbell]

I believe this affects us on v19.