[improvement] fix some successfully precommitted cannot be aborted lead to LabelAlreadyExists

[JNSimba]

Proposed changes

Issue Number: close #xxx

Problem Summary:

1. In the case of writing to multiple tables, such as tables A, B, and C, if tables D and E are added during the period (there is no streamloader for this table in the previous Checkpoint), in the precommit phase, if table D succeeds but table E fails, this will retry from the last Checkpoint, but there is no streamloader of table D in the last checkpoint, so the txn of table D that has been successfully precommitted cannot be aborted, and the error LabelAlreadyExists will be reported next time

2. In the scenario of writing to multiple tables, if the sink is multi-concurrent,
   At this time, the A thread reports an error, and the B thread Http request has ended, and the txnid of successful precommit has not been obtained. However, when jobmanager tries to cancel thread B, the txnid of thread B may not be aborted in time, and an error labelAlreadExist will be reported next time.

Therefore, when the thread exits, it must be aborted according to the label (only available on doris 2.1+)

3. The simultaneous asynchronous check thread is closed in the case of multiple tables.
4. During abort, it is currently based on txnidabort, so a pre-request with the same label will be initiated first. So if this pre-request abort fails, the label will already exist during the next write.
   For example：
   restore from ck-106
   label107 alread exist，abort label107
   label108 not use,abort fail
   restore from ck-106
   label107 not use,exit abort
   label108 write，label already exists

At this time, you need to actively abort the label and let flink restart

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 [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...

[CalvinKirs]

well done