[Improvement] How to get the schema from the fileset data

### What would you like to be improved?

For the fileset data, there always a lot of files and gather together. How to check and extract the schema is a very important feature, and it is very useful in the data engineer's daily work.
1. Provide the path of the firesets, go through each file, extract the schema
2. If the schema are same, store the schema, path and related information somewhere.
3. If the schema are different, create several schema. For each schema, it has its own path and other related information.
4. The schema is a combination of the key and value pair. The key is the column name, the value is the column type.
5. If the column type is an array or an object(json/dict), store the sub structure along with this column name and column type.

### How should we improve?
We can check how Crawler work in AWS, it will help us to understand the schema extracting process a lot.

There is a [video](https://www.youtube.com/watch?v=p4PiMyNZvks) to show how crawler works.

Below is how the schema looks like after the crawler extract the schema from fileset data.

if the data type is struct(json/dict), then we can store the structure of the value, check the example as blew

Start by reviewing the repository's existing fileset and schema-related entry points, then compare the requested behavior with the AWS Crawler example and linked video. Define how paths, shared schemas, differing schemas, column types, and nested JSON or dictionary structures should be represented. Done means fileset data can be scanned and each resulting schema is associated with its paths and related information.

Written by the indexing model from the issue text.