[feature]add ignore-incompatible option

[vinlee19]

Proposed changes

In previous versions, encountering a source schema that did not align with Doris standards would cause the entire job to fail. This issue was particularly critical when managing source instances that contained thousands of tables. Setting the option --ignore-incompatible true allows the system to bypass incompatible schemas and record the errors in the log. Conversely, setting this option to false triggers an error for mismatched schemas.

For example, consider the following MySQL table creation command:

create table aa/b 
( id int,
 name varchar(30)
)

The table name aa/b does not comply with Doris's table naming rules, leading to a 'create table' exception. If the --ignore-incompatible option is set to true, Doris will overlook this exception and log the error instead. Issue Number: close #xxx

Problem Summary:

Describe the overview of changes.

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