Update memory allocation functions to use allocator user data

[lum1n0us]

fix #4024

[loganek]

LGTM. Just a note here, should we add WASM_MEM_ALLOC_WITH_USER_DATA to a deprecation list and remove it on the next API break? Not sure if having this option disabled causes any performance issues, and I think we could improve the readability of the code by not having yet another configuration option.

[lum1n0us]

FYI: the initial concept

However, I agree with the idea of combining WASM_MEM_ALLOC_WITH_USAGE and WASM_MEM_ALLOC_WITH_USER_DATA. @dongsheng28849455 and @wenyongh , please share your thoughts.

[dongsheng28849455]

I agree with the merger, and it need to be informed that the custom allocator may need to consider compatibility issue.

[lum1n0us]

@loganek about " add WASM_MEM_ALLOC_WITH_USER_DATA to a deprecation list". I observed that there are no definitions for malloc_func, realloc_func, and free_func in wasm_export.h. Therefore, we can't use the gcc deprecated attribute as we normally would to indicate deprecation. My thought is to revise the comments above malloc_func to reflect this, but I'm uncertain if that aligns with the deprecated list you were referring to. Please share your suggestions on how to proceed.