Fix memory leak

[taoeffect]

Problem

There seems to be a significant memory leak in GI that only sometimes occurs.

It might have something to do with serdes, and even if it doesn't, this message suggests a memory leak that needs fixing.

Solution

Fix the memory leak.

[corrideat]

The issue with the memory leak is as follows (this is the rationale behind why there was a memory leak and the fix):

1. It's convenient to have functions to be passed across boundaries (e.g., from the app to the SW). For example, a hook or a callback function.
2. However, structuredClone does not support passing in functions. It does allow passing in MessagePorts, which we can use to proxy functions.
3. These MessagePorts weren't being cleaned up. serializer returns a list of revokables that was being ignored (now they're closed in Close unused message ports group-income#3037).

Why things were the were they were

Normally and conventionally, JavaScript functions don't have a 'lifetime' associated with them, other than going out of scope (like most other JavaScript objects). Closing the port amounts to adding an explicit lifetime to the function.

Why the one-liner solution was rejected

The LLM suggestion of closing the port once the function call resolves is suboptimal because it'd mean that the function can only be called once.

What was done instead

In okTurtles/group-income#3037, the list of revokables is used to clean up ports after the main call succeeds. This still adds an explicit lifetime, but allows for proxied function arguments to be called multiple times.

In this PR:

• The list revokables is extended to include a few more message ports
• Added an argument to disable function proxying entirely. This avoids leaks before they can even happen, and is a good way to prevent them in cases where the caller (the one calling serializer) isn't sending or shouldn't be sending any functions.