Attempting to balance Meteors AGAIN - Part 1 : Number Crunching Edition

The number part : 

- Backup shuttle delay brought from 1 hour to 45 minutes. Let's be honest, even though most players appear content with antaghunting for two to three hours straight, they can't stand this delay
- A wave is no longer 'lol have some meteors'. A wave is now 100 TO 200 METEORS. You are welcome
- Inter-wave delay upped to 30-45 seconds from 10-20. About enough to pop out of cover and get some temporary defenses going
- Meteor spawn delay is 1.5 seconds to 2 seconds. This makes meteors pummel a bit slower and makes up for the bigger waves

The mechanics part : 

- Each meteor wave has an assigned direction. This means the following : 
  - Now the meteors will focus on one side of the station. This does not prevent stragglers (meteors can move diagonally) but massively localizes damage. No more random hull damage around the station, one particular area (or a few) are getting it big time
  - Meteors can now be predicted a bit more, along with increase in wave delays. This'll most likely be useful for the second part of this PR, but for now this allows a smart Engineer to notice the meteors are only striking one side and allow him to rebuild, either opposite or adjacent if he feels lucky
  - This should bring down lag SLIGHTLY. Less ZAS and light calculations (because of the focus) and maybe less spawn looping
- Re-added spawn(0) between meteor spawn and push, just in case it can help
- Meteor random events nerfed across the board. Last less, less meteors, and inbuilt meteor delay means it SHOULD no longer cause round-ending damage. A large meteor wave is still something to worry about

This is the first part of a PR to try and unfuck Meteors, again. Second part will be about assets, since I planned to add more than the barricade kits and spawn landmarks but had to stop it there because lolnoskill
this is why proc arguments exist (so you can pass vars directly from one proc to another instead of using global vars)

Though this should likely just be one big proc for now (easier to handle until someone rewrites all of this properly)