[Umbrella] Add testcontainer utils for integration test.

[RocMarshal]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I had searched in the issues and found no similar issues.

Describe the proposal

Add test-container utils for integration test.

• Support remote standalone session cluster.
• Support yarn deployment mode.

Task list

Ignored. see comments.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

[RocMarshal]

Completed via

• Task: [WIP]Add test-container utils for integration test. #3002
• Hotfix: [Hotfix][CI] Fix the target flink home location setting and extend the status getter timeout. #3003
• Deprecated: [Improvement] Add testcontainer utils for test. #2862

There are still some areas here where there is still room for improvement.

• Maybe could reference to Flink Containers of flink-test-utils-junit

• If the performance of the integration testing class is unstable, it is necessary to add junit5 RetryExtension or junit4 RetryRule to eliminate randomness.

• It is unreasonable to download the Flink release package( 1.17.1 tgz now.) every time CI runs.

• Place all integration test cases under a certain module for unified control. Reduce running frequency, reduce time consumption, and reduce download of Flink release packages.

The current strategy is only aimed at quickly supporting code quality improvement and the introduction of test cases.

CC @wolfboys @GOODBOY008 @wuchunfu