[feature] add write blocking properties to control write blocking.

[CodeCooker17]

Proposed changes

Issue Number: close #xxx

Problem Summary:

Describe the overview of changes.
add three config to control write blocking. Prevent write failure due to cpmpaction not being timely to improve write success rate.
--- max blocking times
"doris.sink.max.blocking.times" = "8",
--- max blocking interval times per blocking
"doris.sink.max.blocking.interval.ms" = "300000",
--- need to blocking write keys
"doris.sink.block.trigger.keys" = "-235,-238,-233"

Checklist(Required)

1. Does it affect the original behavior: (Yes/No/I Don't know)
2. Has unit tests been added: (Yes/No/No Need)
3. Has document been added or modified: (Yes/No/No Need)
4. Does it need to update dependencies: (Yes/No)
5. Are there any changes that cannot be rolled back: (Yes/No)

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[JNSimba]

Will there be any problems with this judgment, for example, it is not -235, but -235 appears?

[CodeCooker17]

In order to prevent misjudgment, you can set a more identifiable key, such as 'err=-235,error-238'

[JNSimba]

Is this parameter similar to sink.max-retries?

[CodeCooker17]

'sink.max-retries' is to specify the maximum number of retries for other exceptions, and 'doris.sink.max.blocking.times' is to specify the maximum number of retries when 'doris.sink.block.trigger.keys' appears, Often in order to ensure the success of data import, 'doris.sink.max.blocking.times' is usually set larger

[gnehil]

After the optimization PR of #140, doris will stream the data when writing in http chuck mode, which to a certain extent avoids the compaction problems caused by large batch data load.
And these exception codes are abnormal phenomena caused by doris failures, so they should be exposed and repaired on the doris side, and should not be blocked during writing.