Bytecode scripting

This changed introduces "real" scripting based on a simple bytecode. The bytecode is defined in bytecode_spec.md. Reflection is used to call go functions associated with each opcode.

Scripts are divided into "code" and "data" blocks by the `0xFF` separator byte. Execution ends when this byte is encountered, or when the maximum number of instructions has been reached. Scripts can load and/or modify any byte contained in either the code or data blocks. This means that scripts can change their own behavior during execution.

The largest limitation of the current interpreter is that it can only operate on byte values. That sets a maximum of 255 for all values (e.g. only 255 bytes in the data block are addressable). This needs to be extended such that multiple bytes can be interpreted as shorts, ints, floats, etc.

The cost calculation is also fairly simplistic, with a specific cost associated with every opcode. This can be refined later.
I'm assuming that this is a script which calls NewSibling(). You should probably take these values and make a variable somewhere. I'm not entirely sure the best way to do this (or sure that it should be done anytime soon), but we should probably have a set of variables representing the 'default' or 'basic' scripts.

At the very lest this line needs some comments.