Version worker <-> engine messages

To ensure that we can modify the message format in the future, we need to ensure that any messages sent from worker <-> engine (or vice-versa) have a version number associated with them (or in the envelope surronding the message). This will allow us to move from something like json to something else (msgpack for example) if we ever desire to in the future (for performance benefits or for schema benefits for example...)