Refactor Bluespec Parameters into Config Infrastructure

[dz333]

In order to make sizes (e.g. of Vectors) parametrizable in BSV, the standard practice is to make a file
full of macro definitions => sadly these cannot be instantiated as part of the module types

(e.g., if we have a LSQ definition which has internal Vectors then we can't instantiate multiple copies of that LSQ module with differently sized vectors unless it is computed based on types of other elements (like data, address, or size).

This is the wrong direction of parameterization (I'd rather say, 'make a structure with 8 entries' than, make a structure whose tags require 3 bits) -> and thus we need to do the weird macro define thing.

TODO for this is figure out a good way to integrate this with our BSV runtime with the eventual goal of threading user specified parameters from the frontend all the way through.