State globals in the new runtime

In the v1 runtime, state is provided as a global object. So you can do stuff like this:

create({
   name: state.data.name
}});

Which is nice and good and simple.

But I'm going to suggest we remove the state global from the v2 runtime.

• The new runtime has a stricter notion of immutable state. A cloned state object should be passed into each operation (it's an open question whether we allow mutation within the operation or if we force an immutable object).
• This ensures the integrity of the state object in each operation, which is critical for reproducing bugs and reporting on what is happening within the job
• But obviously with a global state object we can't do anything to preserve the integrity across operations.

This gives us a problem with legacy code which references global state. But it's easy to migrate!

The issue names no files, entry points, or tests. Start by locating the v2 runtime's state handling and references to the global state object, then determine how cloned state is passed to each operation and how legacy references migrate; done means v2 no longer relies on global state while operation state integrity is preserved.