check max row size when parsing csv

[D3Hunter]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

in #40400, we have check whether a single field exceed the max entry size, but we also need to check this for the whole row, to avoid when the data file is corrupted or the input param doesn't match with the file, and causes the parser mistakenly read a vary long row and cause oom

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

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master

[D3Hunter]

for SQL/Parquet files, as they have syntax, it's quite rare to have a row longer than 128M, so we don't handle them right now.