What problem does this PR solve?

Issue Number: close #61397, close #61396

Problem Summary:

1. The CHANGE statement has been removed. It should be removed everywhere in TiDB.
2. Add SEMCommand needed by the SEM feature. The SEM feature will use it to filter out the SQL.

For example, the new design of SEM may have the following config to restrict the SQL:

{
"restricted_SQL" : {
    "SQL": [
        "BACKUP",
        "RESTORE",
        "ALTER RESOURCE GROUP"
    ],
    "rule": [
        "select_into_file",
        "import_from_disk"
    ],
}
}

This PR implements methods to get "SQL" from a real sql statements. Then we can match them in the sem module.

What changed and how does it work?

1. Add a SEMCommand method to StmtNode, and implement it for all StmtNode.
2. Add tests to make sure every subcommand of ADMIN, SHOW, BRIE are included.
3. Remove all codes related to CHANGE statement.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None