feat: disable the conflict check for a table if it has no downstream mv

[chenzl25]

Is your feature request related to a problem? Please describe.

Recently, I did a batch ingestion performance test which showed that the insert performance between table (180s) and append-only table (30s) has a huge gap. On second thought, I think it is possible to disable the conflict check for a table if it has no downstream mv and that is the case when users do the first batch ingestion of their historical data.

Experiment Result:

#14630 (comment)

#14630 (comment)

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response