Refactor whitespace rules code

[DTW-DanWard]

Refactor code that identifies whether or not to add whitespace (currently not ideal for adding user-configurable options). Change to lambda-based design...?

[DTW-DanWard]

Needs a lot of experiments in conjunction with AST. Rules/rule processing should be along the lines of TokenPrev (some bool logic), TokenCurr (some bool logic), TokenNext (some bool logic) and should also be able to handle override contexts, like alignment around = within hashtables (including nested hashtables) and other scenarios (collapsing short statements? Or just apply those first?)