[Improve] Move get schema logic from Config to ReadonlyConfig

[Hisoka-X]

Purpose of this pull request

This PR main do these thing.

1. Move get shema logic from Config to ReadonlyConfig, CatalogTableUtil will covert Config to ReadonlyConfig, the use it to read schema.
2. Fix the ReadonlyConfig dosen't keep the order of user config. To achieve it, I rewrite the logic of properties to map to replace jackson.
3. Add flatten parameter in ConfigUtil as a option to avoid flattening config key. (In schema config, flatten config key makes parsing the schema tricky)
4. Change CatalogTableUtil::getCatalogTablesFromConfig parameter type from Config to ReadonlyConfig. (In most of time, we invoke it with TableFactoryContext, so we can get ReadonlyConfig directly).

Does this PR introduce any user-facing change?

Yes or no? I rewrite all logic of get schema from config, the expected behavior should remain the same as before, but this is a refactoring of user-facing parts of the code.

How was this patch tested?

add new test.

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update change log that in connector document. For more details you can refer to connector-v2
  2. Update plugin-mapping.properties and add new connector information in it
  3. Update the pom file of seatunnel-dist
• Update the release-note.

[Hisoka-X]

cc @ic4y @ruanwenjun @hailin0

[hailin0]

How to test sort of keys

[Hisoka-X]

How to test sort of keys

In fact the new test treeMapFunctionTest in ConfigUtilTest.java can prove it, but it's not easy to notice, so I modify it, to recheck the order before and after invoke treemap.

[ruanwenjun]

+1