feat: add maxMemoryLimitBeforeRecycle options

[AriPerkkio]

• Closes Add a way to recycle workers when heap limit is reached #56

The implementation is highly inspired by jest-worker's idleMemoryLimit option.

Each worker reports their process.memoryUsage().heapUsed to main thread when they have finished the current task. Main thread compares this limit to pool's new memory limit option and decides whether worker should be terminated and replaced with new one.

[AriPerkkio]

@sheremet-va any thoughts? Maybe you could test this against vitest-dev/vitest#3203 before we merge and release this?

[Aslemammad]

@AriPerkkio Any updates on this PR?

[AriPerkkio]

No updates from my side. I think this should work as is but maybe let's first test this with Vitest's work-in-progress vm isolation.

[sheremet-va]

No updates from my side. I think this should work as is but maybe let's first test this with Vitest's work-in-progress vm isolation.

I did not check it yet, VM support is not on my list yet, but will be in a few weeks. I was planning to release a sort of "road map" where everyone can see open PRs and help. Feel free to test this with an open VM PR yourself and make changes if you need to.

[sheremet-va]

Looks like we can merge this and release a new version.

[AriPerkkio]

Testing this with Vitest and seeing crashes when final round of tests are run and workers are recycled. I think this condition needs some changes:

tinypool/src/index.ts

Line 708 in 28ba15f

if (!this.options.isolateWorkers) pool.workers.maybeAvailable(workerInfo)

Looking into this.