Fix potential native stack overflow in struct/array object creation

[kylo5aby]

Add native stack overflow detection to wasm_array_obj_new(),
wasm_struct_obj_new() to prevent potential stack overflow when those GC objects creation performs deep recursion.

[lum1n0us]

• Native stack overflow checking is a good practice. However, besides that, memory (allocated) is another resource that can be exhausted due to recursion. So, I am considering directly limiting the nesting level to protect against both stack overflow and out-of-memory issues. Please share your comments.
• We need a few regression test cases to cover these scenarios.

[kylo5aby]

• Native stack overflow checking is a good practice. However, besides that, memory (allocated) is another resource that can be exhausted due to recursion. So, I am considering directly limiting the nesting level to protect against both stack overflow and out-of-memory issues. Please share your comments.

for multiple levels of nesting, currently appears to handle this properly(just return NULL, to avoid heap overflow), this behavior seems inherently equivalent to creating numerous struct/array objects. If I'm wrong, please let me know.