Fix wrong deallocation management for JSClosure with FinalizationRegistry

In FinalizationRegistry mode, the `swjs_free_host_function` should
be called with the Swift heap object ID, not the JS closure object ID.
The wrong argument was causing:
- Swift closures to be leaked, because FinalizationRegistry attempted
  to release a JS object ID that was never registered as a Swift closure.
- Unintended deallocation of unrelated closures when a reused JS object ID
  happened to match a valid Swift closure ID by coincidence. This
  eventually led to crashes with `The JSClosure has been already released by Swift side.`

Author: kateinoigakukun

Plugins/PackageToJS/Templates/runtime.mjs

@@ -635,7 +635,7 @@ class SwiftRuntime {
                 const fileString = this.memory.getObject(file);
                 const func = (...args) => this.callHostFunction(host_func_id, line, fileString, args);
                 const func_ref = this.memory.retain(func);
-                (_a = this.closureDeallocator) === null || _a === void 0 ? void 0 : _a.track(func, func_ref);
+                (_a = this.closureDeallocator) === null || _a === void 0 ? void 0 : _a.track(func, host_func_id);
                 return func_ref;
             },
             swjs_create_typed_array: (constructor_ref, elementsPtr, length) => {

Runtime/src/index.ts

@@ -553,7 +553,7 @@ export class SwiftRuntime {
                 const func = (...args: any[]) =>
                     this.callHostFunction(host_func_id, line, fileString, args);
                 const func_ref = this.memory.retain(func);
-                this.closureDeallocator?.track(func, func_ref);
+                this.closureDeallocator?.track(func, host_func_id);
                 return func_ref;
             },