Revert super_read_only config file changes

[mattlord]

Description

We intended to use super_read_only everywhere by default in #9312. To our surprise, everything worked and it was an easy change. But... it turned out this was because the config file changes didn't actually take effect because we forgot that we need to update the config file contents that are embedded in mysqlctl's rice box. 🙂

When that change was applied in mysqlctl by updating its rice box (using make embed_config) we saw a huge number of test failures as can be seen in: #10094.

We're instead going to revert the config file specific changes here and schedule work to properly add full super_read_only support to Vitess in: #10363.

After all of this the PR ensures that the embedded mysqlctl content is up-to-date with the repo contents and allows us to add a test for this in #10182.

Related Issue(s)

• Follow-up to: Change default for super_read_only to true #9312
• Follow-up to: Update the embedded config data in mysqlctl #10094
• Follow-up to: remove references to MySQL and Percona 5.6 #10295
• Related to: VReplication: use db_filtered user for vstreams #10080
• Blocker for: Unit test to confirm that the mysqlctl rice box is current #10182

Checklist

• "Backport me!" label has been added if this change should be backported
• Tests are not required
• Documentation is not required

[github-actions]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
• If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

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.