Explore: Compiling Blueprints to independent PHP files

Executing Blueprint steps often involves spawning subprocesses, e.g. to activate a WordPress plugin in an independent environment that can crash without crashing the main PHP process.

However, in runtime like Playground, spawning a PHP sub-process might be expensive as it would require allocating twice the HEAP inside the browser and potentially require downloading PHP.wasm again.

Let's test the performance of in-browser sub-processes, and if it's bad, then Blueprints could be compiled as follows:

1. Run PHP to turn a Blueprint into a series of smaller PHP files like step0.php, step1.php etc.
2. Each file is an isolated container and is free to, e.g., include wp-load.php
3. TypeScript runtime would run those files one by one. The PHP runtime would do the same thing.

Start by benchmarking in-browser PHP subprocesses, focusing on the cost of allocating another HEAP and downloading PHP.wasm again. If that approach performs poorly, evaluate compiling a Blueprint into isolated files such as step0.php and step1.php, then confirm that the TypeScript and PHP runtimes can execute them one by one.