Better constants management (config files?)

[calebchalmers]

There are a lot of constants for our robots and each type has a full set of definitions. Considering how much overlap there is between robot types, could we generalize more? Can we use a schema?

Also, robots might have the need for constants relevant only to them, but currently, those constants must be defined for all robot types in order to avoid compilation errors.

One option would be to have a pre-compilation script which takes a config file (perhaps YAML or JSON) and then generates a C++ header with the relevant constants.