Added novice and respawn zones to runtimeData

[SyluxImmortal]

This caches the novice and respawn zone values and places them into runtimeData each tick. This cache is cleared once a tick, but could be setup to cache until the nearest novice/respawn zone will expire. The reason I didn't set it up this way is because I do not know the exact procedures on novice/respawn zone creation, so I do not know if they can invalidate the cache.

I have not tested this with IVM, but a quick glance through the ivm branch suggests it should work the same way, but I could be very wrong on that.

This is an attempted revision of this concept:
screeps/engine#88

This is the PR to access these dates:
screeps/engine#89

It's worth noting that some other files could be refactored to use this data. The primary example being the nuker structure.

[artch]

Unfortunately, we're not accepting PRs that introduce performance-sensitive functionality to the low level runtime/processor driver loops such as additional direct database requests. Properly optimizing them in our main world cluster is very sophisticated, and we don't want to differentiate community server driver and our cluster driver too much if we're not able to merge them easily.

This functionality will probably be introduced in official patches in the future, thank you for your contribution anyway.