[BUG] Catch retry submit exception

[xinghuayu007]

Proposed changes

When Load Job Task Queue is filled, continue to submit more jobs to the queue will cause RejectedExecutionException. But callback.onTaskFailed function does not catch the exception, that will cause re-submitting job failed, and status is not updated to failed.
issue: #4795

Types of changes

What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• [] New feature (non-breaking change which adds functionality)
• [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [] Documentation Update (if none of the other choices apply)
• [] Code refactor (Modify the code structure, format the code, etc...)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have create an issue on (Fix [BUG] retry submit exception is not catched #4795), and have described the bug/feature there in detail
• Compiling and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• If this change need a document change, I have updated the document
• Any dependent changes have been merged

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...

[morningman]

Some other parts need to be fixed too:

[EmmyMiao87]

Another problem is that I think loading should not have so much concurrency control.
In fact, db itself already has a control of the number of transactions.
So the number of concurrent tasks here is best to be twice the number of transactions.

Also, if the submitted task is abnormal, I think the load job can be cancelled directly.
The reason is that after the system is currently loading the stack, it is generally difficult to recover quickly, so you are not sure how long you will have to wait to retry successfully.

[morningman]

LGTM

[EmmyMiao87]

LGTM