Plan replayer requires additional option on connection string when using MySQL

Change Request

Please answer the following questions before submitting your issue. Thanks!

1. Describe what you find is inappropriate or missing in the existing docs.

https://docs.pingcap.com/tidb/dev/sql-plan-replayer

When using plan replayer, import can fail when connecting as MySQL. There is no documented solution or visibility to this issue on the plan replayer page.

2. Describe your suggestion or addition.

When using plan replayer, it you are using MySQL - you will want to include the recommendation that can be found on this documentation page:
https://docs.pingcap.com/tidbcloud/tidb-cloud-import-local-files

The recommendation from that page is:
If you use mysql and encounter ERROR 2068 (HY000): LOAD DATA LOCAL INFILE file request rejected due to restrictions on access., you can add --local-infile=true in the connection string.

3. Provide some reference materials (such as documents and websites) if you could.

Reference provided is from an existing PingCAP documentation page.

Open the SQL Plan Replayer page at https://docs.pingcap.com/tidb/dev/sql-plan-replayer and review the import instructions. Compare them with the guidance in https://docs.pingcap.com/tidbcloud/tidb-cloud-import-local-files, then add the MySQL --local-infile=true recommendation and error context. Done means the Plan Replayer page visibly explains how to avoid this import failure when connecting with MySQL.