upgrade to v6.0.0 fail when old cluster include stmt-summary config

[seiya-annie]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

1. install v5.4.0 with config:
   stmt-summary.enable
   stmt-summary.enable-internal-query
   stmt-summary.history-size
   stmt-summary.max-sql-length
   stmt-summary.max-stmt-count
   stmt-summary.refresh-interval
2. upgrade to 6.0.0

2. What did you expect to see? (Required)

stmt-summary config can be ignored during upgrade

3. What did you see instead (Required)

upgrade fail
Error: init config failed: 172.16.5.101:4000: executor.ssh.execute_failed: Failed to execute command over SSH for '[email protected]:22' {ssh_stderr: , ssh_stdout: [2022/03/23 12:48:15.840 +08:00] [FATAL] [terror.go:292] ["unexpected error"] [error="config file /home/tidb/deploy/tidb-4000/conf/tidb.toml contained invalid configuration options: enable-streaming, stmt-summary, stmt-summary.enable, stmt-summary.enable-internal-query, stmt-summary.history-size, stmt-summary.max-sql-length, stmt-summary.max-stmt-count, stmt-summary.refresh-interval; check TiDB manual to make sure this option has not been deprecated and removed from your TiDB version if the option does not appear to be a typo"]

4. What is your TiDB version? (Required)

v6.0.0 2022-03-22T19:47:19+08:00

[seiya-annie]

@morgo hi, why these stmt-summary configs are not ignored during upgrade