Make emscripten_resize_heap compatible with PURE_WASI

Previosly, using PURE_WASI was incompatible with
EMSCRIPTEN_MEMORY_GROWTH flag, and was not documented.

Now, using EMSCRIPTEN_MEMORY_GROWTH with PURE_WASI is
possible. It will not require the host to export
emscripten_notify_memory_growth and will grow the memory
as expected from EMSCRIPTEN_MEMORY_GROWTH.

Fixes #22211

Signed-off-by: inkeliz <inkeliz@inkeliz.com>

Author: inkeliz

system/lib/standalone/standalone.c

@@ -152,7 +152,7 @@ size_t emscripten_get_heap_max() {
 }
 
 int emscripten_resize_heap(size_t size) {
-#if defined(EMSCRIPTEN_MEMORY_GROWTH) && !defined(EMSCRIPTEN_PURE_WASI)
+#if defined(EMSCRIPTEN_MEMORY_GROWTH)
   size_t old_size = __builtin_wasm_memory_size(0) * WASM_PAGE_SIZE;
   assert(old_size < size);
   ssize_t diff = (size - old_size + WASM_PAGE_SIZE - 1) / WASM_PAGE_SIZE;
@@ -161,8 +161,10 @@ int emscripten_resize_heap(size_t size) {
   // (uint32_t)-1 even with memory64:
   // https://bugs.chromium.org/p/v8/issues/detail?id=13948
   if (result != (uint32_t)-1 && result != (size_t)-1) {
+#if !defined(EMSCRIPTEN_PURE_WASI)
     // Success, update JS (see https://github.com/WebAssembly/WASI/issues/82)
     emscripten_notify_memory_growth(0);
+#endif
     return 1;
   }
 #endif