Enforce consistent code style

[LeoCodes21]

There are many different naming conventions currently in use in the various support modules. Although class names should not be changed, property names can (and should) be changed and made consistent. Other style rules might include:

• spacing enforcement (indentation and such)
• constructor location (should be below properties)
• member initialization (reference types must be set to a non null value unless there's a reason not to) (see All officially implemented types should not have null values #5)

Ideally, multiple people can work on this.

[LeoCodes21]

Another thing to note: enums should never inherit from uint, as sometimes signed values are desired (e.g. for "invalid" values.) A few enums currently inherit from uint rather than int.