issues handling importing csv with date typed fields

[wey-gu]

Describe the bug (must be provided)

It seems when a field with type date was configured in the studio, with a field like 2020-01-01 in CSV, it will fail.
Whereas in importer, it should be working:

---

https://github.com/vesoft-inc/nebula-importer/blob/617990914cfe30a906351f3eb2f7ca697555dfd4/examples/v2/example.yaml#L415-L435

https://github.com/vesoft-inc/nebula-importer/blob/master/examples/v2/date_test.csv

Your Environments (must be provided)

• OS: Linux,Mac or Windows
• Node-version: node --version
• Studio-version: v3.2.3

How To Reproduce(must be provided)

Steps to reproduce the behavior:

1. Step 1 create schema like

2. Step 2 prepare data like

"v1",2020-01-01
"v2",2020-01-02

3. Step 3 import like

4. It failed as:

$ docker logs nebula-graph-studio-v323_web_1 --since 20m
[INFO] 2022/04/01 02:04 200 1.175753ms 192.168.9.3 PUT /api/files
[INFO] 2022/04/01 02:04 200 191.017µs 192.168.9.3 GET /api/files
[INFO] 2022/04/01 02:04 200 1.999393ms 192.168.9.3 POST /api-nebula/db/exec
[INFO] 2022/04/01 02:04 200 2.166102ms 192.168.9.3 POST /api-nebula/db/exec
[INFO] 2022/04/01 02:04 200 1.558106ms 192.168.9.3 POST /api-nebula/db/exec
1.6487787003726132e+09	warn	controller/gateway.go:56	gql execute fail	{"error": "-1005:Storage Error: The data type does not meet the requirements. Use the correct type of data."}

Expected behavior

Import successfully

Additional context

Provide logs and configs, or any other context to trace the problem.

[hetao92]

we will fix this in v3.3.0