[FLINK-35758][doc][cdc-connector][mysql] Add missed scan.startup.timestamp-millis option for mysql connector

This closes  #3453.

Author: lvyanquan

docs/content.zh/docs/connectors/flink-sources/mysql-cdc.md

@@ -285,6 +285,13 @@ Flink SQL> SELECT * FROM orders;
       <td>String</td>
       <td>在 "specific-offset" 启动模式下，启动位点的 GTID 集合。</td>
     </tr>
+    <tr>
+      <td>scan.startup.timestamp-millis</td>
+      <td>optional</td>
+      <td style="word-wrap: break-word;">(none)</td>
+      <td>Long</td>
+      <td>在 "timestamp" 启动模式下，启动位点的毫秒时间戳。</td>
+    </tr>
     <tr>
       <td>scan.startup.specific-offset.skip-events</td>
       <td>optional</td>

docs/content.zh/docs/connectors/pipeline-connectors/mysql.md

@@ -172,8 +172,7 @@ pipeline:
       <td style="word-wrap: break-word;">initial</td>
       <td>String</td>
       <td> MySQL CDC 消费者可选的启动模式，
-         合法的模式为 "initial"，"earliest-offset"，"latest-offset"，"specific-offset" 和 "timestamp"。
-           请查阅 <a href="#a-name-id-002-a">启动模式</a> 章节了解更多详细信息。</td>
+         合法的模式为 "initial"，"earliest-offset"，"latest-offset"，"specific-offset" 和 "timestamp"。</td>
     </tr>
     <tr>
       <td>scan.startup.specific-offset.file</td>
@@ -196,6 +195,13 @@ pipeline:
       <td>String</td>
       <td>在 "specific-offset" 启动模式下，启动位点的 GTID 集合。</td>
     </tr>
+    <tr>
+      <td>scan.startup.timestamp-millis</td>
+      <td>optional</td>
+      <td style="word-wrap: break-word;">(none)</td>
+      <td>Long</td>
+      <td>在 "timestamp" 启动模式下，启动位点的毫秒时间戳。</td>
+    </tr>
     <tr>
       <td>scan.startup.specific-offset.skip-events</td>
       <td>optional</td>

docs/content/docs/connectors/flink-sources/mysql-cdc.md

@@ -283,6 +283,13 @@ Connector Options
       <td>String</td>
       <td>Optional GTID set used in case of "specific-offset" startup mode</td>
     </tr>
+    <tr>
+      <td>scan.startup.timestamp-millis</td>
+      <td>optional</td>
+      <td style="word-wrap: break-word;">(none)</td>
+      <td>Long</td>
+      <td>Optional millisecond timestamp used in case of "timestamp" startup mode.</td>
+    </tr>
     <tr>
       <td>scan.startup.specific-offset.skip-events</td>
       <td>optional</td>

docs/content/docs/connectors/pipeline-connectors/mysql.md

@@ -175,8 +175,7 @@ pipeline:
       <td>optional</td>
       <td style="word-wrap: break-word;">initial</td>
       <td>String</td>
-      <td>Optional startup mode for MySQL CDC consumer, valid enumerations are "initial", "earliest-offset", "latest-offset", "specific-offset" and "timestamp".
-           Please see <a href="#startup-reading-position">Startup Reading Position</a> section for more detailed information.</td>
+      <td>Optional startup mode for MySQL CDC consumer, valid enumerations are "initial", "earliest-offset", "latest-offset", "specific-offset" and "timestamp".</td>
     </tr>
     <tr>
       <td>scan.startup.specific-offset.file</td>
@@ -199,6 +198,13 @@ pipeline:
       <td>String</td>
       <td>Optional GTID set used in case of "specific-offset" startup mode</td>
     </tr>
+    <tr>
+      <td>scan.startup.timestamp-millis</td>
+      <td>optional</td>
+      <td style="word-wrap: break-word;">(none)</td>
+      <td>Long</td>
+      <td>Optional millisecond timestamp used in case of "timestamp" startup mode.</td>
+    </tr>
     <tr>
       <td>scan.startup.specific-offset.skip-events</td>
       <td>optional</td>