Update RETL Query Length Limit

Hi, I am on the RETL team and we noticed that in our public docs we are using an erroneous value for the query length. For the `query` column in our MySQL DB we use MYSQL `TEXT` which has a character limit of 65,535. When a customer/user saves anything longer than that it auto truncates to that limit, which will lead to the query failing.

Author: Lfdelossantos

src/connections/reverse-etl/system.md

@@ -38,7 +38,7 @@ If you have a non-standard or high volume usage plan, you may have unique Revers
 
 Name | Details | Limit
 --------- | ------- | ------
-Model query length | The maximum length for the model SQL query. | 131,072 characters
+Model query length | The maximum length for the model SQL query. | 65,535 characters
 Model identifier column name length | The maximum length for the ID column name. | 191 characters
 Model timestamp column name length | The maximum length for the timestamp column name. | 191 characters
 Sync frequency | The shortest possible duration Segment allows between syncs. | 15 minutes
@@ -56,4 +56,4 @@ Column JSON size | The maximum size of any single column value. | 128 KiB
 
 <sup>*</sup>: _If Segment identifies a sync would be larger than 150 million records, Segment extracts 150 million of the records in the initial sync and syncs any additional records during the next scheduled or manual sync._ 
 
-_For example, if a sync would contain 700 million records, Segment would run an initial 150 million record sync, and during the next three scheduled or manual syncs, would sync 150 million records. The fifth scheduled or manual sync would contain the remaining 100 million records._ 
+_For example, if a sync would contain 700 million records, Segment would run an initial 150 million record sync, and during the next three scheduled or manual syncs, would sync 150 million records. The fifth scheduled or manual sync would contain the remaining 100 million records._