Fix wasm table access when accessing functions in splitted module (#25432)

When accessing functions from the splitted module, there's an error
because the wasmtable is using table64. So we would have to access it
with a BigInt. This has been updated in other part of the codebase, but
we missed this file.

Author: Mintyboi

src/preamble.js

@@ -503,10 +503,9 @@ var splitModuleProxyHandler = {
       // When the table is dynamically laid out, the placeholder functions names
       // are offsets from the table base. In the main module, the table base is
       // always 1.
-      return wasmTable.get(1 + parseInt(prop))(...args);
-#else
-      return wasmTable.get(prop)(...args);
+      prop = 1 + parseInt(prop);
 #endif
+      return wasmTable.get({{{ toIndexType('prop') }}})(...args);
 #endif
     }
   }

test/test_other.py

@@ -12816,6 +12816,7 @@ def test_syslog(self):
   def test_syscall_stubs(self):
     self.do_other_test('test_syscall_stubs.c')
 
+  @also_with_wasm64
   @parameterized({
     '': (False, False, False),
     'custom': (True, False, False),
@@ -12848,6 +12849,8 @@ def test_split_module(self, customLoader, jspi, opt):
                       '--export-prefix=%', 'test_split_module.wasm.orig', '-o1', 'primary.wasm', '-o2', 'secondary.wasm', '--profile=profile.data']
     if jspi:
       wasm_split_run += ['--jspi', '--enable-reference-types']
+    if self.get_setting('MEMORY64'):
+      wasm_split_run += ['--enable-memory64']
     self.run_process(wasm_split_run)
 
     os.remove('test_split_module.wasm')