Introduce a separate SQL module for shading the dependencies.

By default, the rocketmq-flink jar file contains too many unnecessary dependencies (flink-core/flink-runtime/flink-client/flink-avro/flink-streaming-java/powermock/logback ......)that can easily lead to dependency conflicts.

In the default connector module, we should not perform shading, and we should introduce a separate SQL module for shading the required dependencies. We need to relocate the shaded jar files to avoid conflicts.

Start by inspecting the default connector module's build configuration and its current dependency list, then identify the required dependencies for the separate SQL module. Verify how shading and relocation are configured and confirm that the default connector no longer shades unnecessary dependencies while the SQL artifact contains only the intended relocated dependencies.

Written by the indexing model from the issue text.