Don't always export writeStackCookie/checkStackCookie. NFC (#17426)

At some point these were used via the Module object but that is no
longer the case so there is no need to export them.

See #12630 for when the last such usage was removed.

The code size regressions are only in ASSERTIONS builds and they are due
to the assertions being present to check for unexported runtime methods.

Author: sbc100

emcc.py

@@ -1912,7 +1912,6 @@ def phase_linker_setup(options, state, newargs, user_settings):
     if settings.WASM2JS:
       exit_with_error('WASM2JS is not compatible with relocatable output')
     # shared modules need memory utilities to allocate their memory
-    settings.EXPORTED_RUNTIME_METHODS += ['allocate']
     settings.ALLOW_TABLE_GROWTH = 1
 
   # various settings require sbrk() access

emscripten.py

@@ -156,7 +156,6 @@ def update_settings_glue(wasm_file, metadata):
     settings.DEFAULT_LIBRARY_FUNCS_TO_INCLUDE += ['$allocateUTF8OnStack']
 
   if settings.STACK_OVERFLOW_CHECK and not settings.SIDE_MODULE:
-    settings.EXPORTED_RUNTIME_METHODS += ['writeStackCookie', 'checkStackCookie']
     # writeStackCookie and checkStackCookie both rely on emscripten_stack_get_end being
     # exported.  In theory it should always be present since its defined in compiler-rt.
     assert 'emscripten_stack_get_end' in metadata['exports']

tests/other/metadce/test_metadce_hello_O0.jssize

@@ -1 +1 @@
-26713
+26718

tests/other/metadce/test_metadce_minimal_O0.jssize

@@ -1 +1 @@
-21410
+21422

tests/other/test_unoptimized_code_size.js.size

@@ -1 +1 @@
-94954
+94964