Module Overloading

[VonTum]

We can do module overloading at the Abstract Typing Level. That makes it such that modules can still be navigated reliably (so no C++-style parsing idiocy), while allowing for overloaded naming. Given that we don't intend to add traits, it means that with module overloads it isn't possible to dynamically "pick" an implementation based on template arguments. To me that seems like a fair tradeoff, since highly generic hardware development isn't a goal of SUS.

Synergises very well with #58, such that we can have operator overloading for other types, like float (See #27)