Removes caching for creating and removing Bastions

This may obviously cause some extra lag, but I suspect if anything it will actually cut back on lag spikes. The way I'm currently doing things the same number of requests will get sent to the sql server as before, but they will now be more spread out. Updating the balance (the fractional part of the strength) and the placed time is still cached as before, but I've changed the way those values are updated to actually be done properly rather than deleting and resaving them. My hope is that with this more straight forward method of saving and deleting there will not be problems with creating ghost fields. 

Some other small fixes include removing a line that was removing the balance information on load (don't ask my why) and some changes to the names and locations of functions.

As always I've done my best to test all this but if accepted it should probably go on civtest first for some more broad tests. As I can't reproduce any of the other bugs mentioned this unlikely to fix them.