Add file locking integration tests for php-wasm/node

[brandonpayton]

Motivation for the change, related issues

We have automated tests for our file lock manager but no integration tests to demonstrate locking is working between @php-wasm/node instances. Let's fix that.

Implementation details

This PR:

• Adds automated tests for file locking within @php-wasm/node
• Fixes a bug discovered by the additional tests: releasing flock() locks when the associated file descriptor is closed.

The tests coordinate between two or more concurrent @php-wasm instances using a simple text file to gate the stages. For example, for php instances php1 and php2 testing exclusive locking:

• File initially contains "php1-locking"
• php1 starts without waiting
• php2 waits until file contains "php1-waiting-for-php2-to-try"
• php1 obtains an exclusive lock on a SQLite DB and sets file contents to "php1-waiting-for-php2-to-try"
• php1 waits until file contains "php2-ready-for-unlock"
• php2 attempts to write to DB, records the outcome, and sets file contents to "php2-ready-for-unlock"
• php2 waits until file contains "php1-unlocked"
• php1 unlocks the DB, sets file contents to "php1-unlocked", and exits
• php2 repeats its attempt to right the DB, records the outcome, echoes its results, and exits
• the test case asserts expected outcome

Maybe there is a better way to coordinate between instances, but so far, this seemed the most straightforward.

Once these tests are fleshed out, we can probably add nearly identical tests for Playground CLI, but run the scripts via HTTP requests.

Testing Instructions (or ideally a Blueprint)

• CI

[brandonpayton]

I had Claude try to fill in the remaining outlined tests. I haven't reviewed or refined the results yet, but one of the failing tests was for a real reason:

flock() locks are not currently released when their associated file descriptor is closed. This is a bug, and I've pushed a fix. But the php-wasm/node rebuild will have to complete overnight. (Note: A rebuild wouldn't be required here if we manage to land something like #2891 to move our Emscripten syscall customization into separate modules that are injected at runtime)

[brandonpayton]

This is ready for review. This PR contains php-wasm/node rebuilds to fix a flock() bug. I would consider just merging to avoid the possibility of needing to rebuild again due to conflict, but I'd rather not merge right before going to bed.

After this PR, we can add equivalent tests for Playground CLI. They should be about the same but triggered via HTTP requests.

[adamziel]

This feels weird but I get why we need it.