[INLONG-10703][Manager] Manager Add Oceanbase Support

[xxsc0529]

Fixes #10703

Motivation

Added support for Oceanbase data sources to adapt to the Oceanbase ecosystem. close #10703

Modifications

It mainly adds oceanbase data source support and uses the oceanbase-client driver to connect.

It mainly adds oceanbase data source support and uses the oceanbase-client driver to connect. And write oceanbase's ExtractNode logic and LoadNode logic. The specific implementation logic is the same as mysql.Added support for oceanbase on the front-end page. Since the jdbc-inlong processing logic in the flink15 connection lacks the jdbc dialect, an error is reported. This is modified here.

Verifying this change

(Please pick either of the following options)

• This change is a trivial rework/code cleanup without any test coverage.

• This change is already covered by existing tests, such as:
  (please describe tests)
  Here's how the page test works
  
  
  
  

• This change added tests and can be verified as follows:
  Please use the following test classes for testing org.apache.inlong.sort.parser.MySqlExtractNodeToOceanBaseLoadNodeTest
  (example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Documentation

• Does this pull request introduce a new feature? (yes / no) yes
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) Data source types have been added to the README.md
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

[xxsc0529]

please add test result with real data from any source to oceanbase
What kind of test data is needed and where to put it

[dockerzhang]

@xxsc0529 please fix the failed workflow and comments, thanks.

[xxsc0529]

@xxsc0529 please fix the failed workflow and comments, thanks.

This codeQL doesn't work.,The same logic as mysql here.,I can't detect a lot of the original code here.,Do you have to solve this problem?，If you look at this diagram, the original code containing the DriverManager.getConnection logic did not pass codeQl

[dockerzhang]

@xxsc0529 you could ignore the CodeQL fails, but it's better to click resolve if you fix the comments.

[xxsc0529]

resolve

Resolved