Fix how we generate the query serving error documentation

[frouioui]

Description

A small change introduced to our error code led to the query serving error documentation generation to not work as expected: It was trying to parse the arguments (%s, %d, etc) in the strings and was printing things like '%!s(MISSING)' instead of '%s'. The issue is visible in this PR, specifically this commit: vitessio/website@98b15a1 (#1905).

We should backport this to 21.0 as the issue was first introduced there.

I have updated vitessio/website#1905 with the newly generated docs for each branch (from 19 to main).

[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 67.70%. Comparing base (ec29bdb) to head (9ee6bee).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17516      +/-   ##
==========================================
- Coverage   67.71%   67.70%   -0.02%     
==========================================
  Files        1584     1584              
  Lines      254519   254524       +5     
==========================================
- Hits       172338   172313      -25     
- Misses      82181    82211      +30     

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