[fix](fe) Fix OceanBase JDBC catalog compatibility with newer drivers

[hubgeter]

What problem does this PR solve?

Problem Summary:
OceanBase JDBC catalog worked with oceanbase-client-2.4.8, but failed with newer drivers such as 2.4.15, 2.4.16, and 2.4.17.

The main background is:

• newer OceanBase JDBC drivers changed the metadata returned by DatabaseMetaData.getColumns()
• type names became lowercase
• unsigned information is no longer preserved in the same way
• some columns were mapped to UNSUPPORTED_TYPE, so DESC and query failed
• with 2.4.17, timestamp/datetime values could also be read with an incorrect timezone offset

This PR fixes the compatibility in two parts:

• improve OceanBase/MySQL type parsing by using normalized type definitions and raw column type information from SHOW FULL COLUMNS
• add OceanBase driver version based JDBC URL handling so newer drivers use the correct datetime behavior

After this change, OceanBase JDBC catalog can work correctly with:

• oceanbase-client-2.4.15
• oceanbase-client-2.4.16
• oceanbase-client-2.4.17

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[hubgeter]

run buildall

[hubgeter]

run buildall