[BitSail][Features] Support list and map in current FileMappingTypeInfoConverter

[kyle-hawk]

Signed-off-by:

Pre-Checklist

Note: Please complete ALL items in the following checklist.

• I have read through the CONTRIBUTING.md documentation.
• My code has the necessary comments and documentation (if needed).
• I have added relevant tests.

Purpose

• close [BitSail][Features] Support list and map in current FileMappingTypeInfoConverter. #251

Approaches

For complex types like list and Map, use BitSail type string as the bridge between engine type string and typeInfo, and convert engine type string like Map(String,Map(String,Int32)) into map<string,map<string ,int>> such BitSail type string, and then realize the conversion between BitSail type string and typeInfo through BitSailTypeParser

Related Issues

• close [BitSail][Features] Support list and map in current FileMappingTypeInfoConverter. #251

New Behavior (screenshots if needed)

N/A

[hk-lrzy]

maybe we didn't need this part, we can consider it as default

[hk-lrzy]

maybe we didn't need this part, we can consider it as default

[kyle-hawk]

I do this because I want to leave an entry for connector developers so that they can make the engine type string as close as possible to the type description of the engine itself. I think this has two advantages:

1. It can constrain the field types configured by users ;
2. Users have a clearer principle to know how to configure the engine type—consistent with the original type of the engine. Type configurations such as int32 and double64 will make users doubtful

@hk-lrzy look forwards ur further advice