REP-819 Keystone V3 Filter

The mess that is Keystone v3! Comment on _everything_ so we can get this fixed up. =)
They maintain code clarity while reducing length? We don't have to make the same method calls multiple times? All of the config parsing is done in the same block of code? We get immutable values so that if the keystoneConfig object changes underneath us we don't care (although lazy evaluation means that's still a threat if it happens before the first time we need the value, but lazy has other benefits)?

I like having these values declared and being able to use the shortened names. Is there a reason we should remove them?