[FLINK-29087][connector/jdbc] change dependencies order to avoid compile failure while running idea

[xuyangzhong]

What is the purpose of the change

Currently, we rewrite calcite to full its logic on Flink. But in connector-jdbc pom.xml, the wrong order about "flink-table-planner" and "flink-table-planner" (test-jar) will cause idea to fail when running MySqlCatalogITCase. This reason is that the wrong order causes idea to load calcite-1.26 first and then load table-planner, and the rewritten files do not work actually.

BTW, compiling and testing by maven, and other pom.xml will not be affected.

Brief change log

• change dependency order about "flink-table-planner" and "flink-table-planner" (test-jar).

Verifying this change

This change is already covered by existing tests 'MySqlCatalogITCase'

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented?

[flinkbot]

CI report:

• 8f90b2e Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[lsyldliu]

LGTM

[leonardBang]

Thanks @xuyangzhong for the improvement, could you explain why test-jar will influence the dependency load order?