Previously, PropertyManager used SerializedShardDatabase to wrap it's database calls.
This didn't make much sense because SerializedShardDatabase was basically just a wrapper that serialized calls to ShardDatabase.
So, instead, we now have a ShardConfigDatabase class as well that is held by DatabaseManager. This holds the property/config specific funcitons for the shard.
In addition, there were a couple bugs fixed in PropertyManager where a function migt have been GetLong() when it should have been GetDouble(), etc...
