Fix an export name check exception

[lum1n0us]

No description provided.

[yamt]

this fix doesn't seem right.
if we want to support names including '\00', we should stop using strlen etc.

[lum1n0us]

we are thinking about using an extra length field to store the length of a string, in our case an unicode string.

It seems both import name and export name need to face gaps between cstyle name and unicode name:

• an unicode name may start with a \0
• an unicode name may not end with a \0

Definity, we need an extra field to store name's length and use binary operations to replace "<string.h>" operations when dealing with import names and export names.

Need to do include modifications about:

• Store Wasm import names and export names in unicode string instead of c-style string
• Process(mostly comparison) import names and export names in a way of binaries. It includes linking(w/ import names), calling from outside(w/ export names)
• (Optional) handling unicode strings in REPL
• (Partial implement) Store import name and export name in unicode string in AOT file
• Use unicode strings in const string pool of both Wasm loader and AOT

It is requires by Spec. But, is it a good idea to support unicode string as import name and export name? A lot modification Vs. unusual benefit. We tend to put a limitation of import names and export names that only c-style names are allowed.

name in string	name in binary		support?
	length	bytes
""	00	00	Y
"a"	01	61	Y
"\61"	01	61	N
"\00"	01	00	N
"\00\01"	02	00 01	N
"\01\00\02"	03	01 00 02	N
"\61\00"	02	61 00	N

[wenyongh]

LGTM