should verify the type mismatch when insert or update

[nebula-bots]

if the type of property is datetime, and then insert or update with string, should be prevented by graph validator.

actual:
send to storaged.

should be SemanticError not storage error

(root@nebula) [sf100]>  update vertex on Person 933 set firstName=23 when firstName == "harris"
Execution succeeded (time spent 592/14224 us)

Wed, 09 Nov 2022 16:31:08 CST

(root@nebula) [sf100]>  update vertex on Person 933 set firstName=23
[ERROR (-1005)]: Storage Error: Invalid data, may be wrong value type.

Wed, 09 Nov 2022 16:31:51 CST


(root@nebula) [sf100]> desc tag Person
+----------------+----------+-------+---------+---------+
| Field          | Type     | Null  | Default | Comment |
+----------------+----------+-------+---------+---------+
| "firstName"    | "string" | "YES" |         |         |
| "lastName"     | "string" | "YES" |         |         |
| "gender"       | "string" | "YES" |         |         |
| "birthday"     | "string" | "YES" |         |         |
| "creationDate" | "string" | "YES" |         |         |
| "locationIP"   | "string" | "YES" |         |         |
| "browserUsed"  | "string" | "YES" |         |         |
+----------------+----------+-------+---------+---------+
Got 7 rows (time spent 629/13654 us)

Wed, 09 Nov 2022 16:41:35 CST

(root@nebula) [sf100]> INSERT VERTEX t5(p1, p2, p3) VALUES 1:("Abe", 2, 3);
Execution succeeded (time spent 1070/13328 us)

Wed, 09 Nov 2022 16:34:06 CST

(root@nebula) [sf100]> INSERT VERTEX t5(p1, p2, p3) VALUES 1:("Abe", "2", 3);
[ERROR (-1005)]: Storage Error: The data type does not meet the requirements. Use the correct type of data.

[dutor]

IMO, This should have been handled by the query engine. But given the fact that all of the type checking in INSERT or UPDATE is fallen into the storage layer, the refactoring work is considerable.
Better to let it go at the moment.