Give bots their resource constraints as parameters

[jmcarthur]

In particular, give them the maximum amount of memory they are allowed to use, but I'm making the name of this issue a bit more general in case there are other ideas to add to it. We designed the "turn 0" parameters to be extensible, so this shouldn't be too much of an impact. However, we apparently never mentioned this extensibility in the spec so far (I intend to add that point to it after posting this issue, though), so it is possible that this would break some of the bots in the beta.

I think this is a reasonable addition, but I'm posting an issue instead of just making a patch because I want to first make sure there are no objections.

[mleise]

Additional info: Some people already made the assumption, that the parameters don't change. When the player_seed was added I heard from a participant that the bot crashes because the new keyword was unexpected. Other bots, like the C starter use only sample one or two characters from the keyword to identify the parameter.
So when this is done we need to check the source codes of starter bots for any 'misunderstandings' and test them again. In any case an update to the specs would be nice. It should also tell that the int must be at least signed 64-bit (as in the case of the player seed. Hmm, now that I think about it, JavaScript cannot store arbitrary 64-bit ints, because it is floating-point based. Oh this gets complicated, I'm out.