Module patterns should actually be arbitrary hierarchical prefixes/contexts

[clairexen]

The current design document has a strict separation of "module patterns", and "net patterns" that look up net names within that module. But what we actually want long-term is to support any hierarchical prefix in those module patterns, so that we are independent of flattening.

Thus, when we process the databases of IDs, we have to look at the original gold design hierarchy before combining and flattening, and collect all those prefixes, and then create a database with all proper module names.

Then, when we have a match for a "module pattern", we have to remove the part that matches the actual module ind the partially flattened design, and use the rest (with a dot appended at the end) as an implicit prefix for matching the net patterns within the matching module. (And for names that we assign to partitions, we also need to add that prefix to the user-supplied partition names.)