fix conflict specification included in module files

fix conflict specification included in module files (see #994), base it on short module name obtained from active module naming scheme

this forced me to resort to another solution for verifying toolchain definitions vs the loaded toolchain module, since this basically means we can no longer obtain the (isolated) software name from a given module file (keeping in mind that a custom module naming scheme may be embedded a software name in some weird way)

the inner function `tc_elem_present` now using a regex to check whether a module name *could* be for a software package with the specified name, which is the best I can come up with

this approach should work most of the time, but it possible to come with a (weird) module naming scheme that breaks the assumptions made in `tc_elem_present`...
reversability is not mandatory in this case. worst case you inspect all modules to find the ones with matching name :smile: 
but it would really help if this is delegated to the naming scheme. 
then people who do stupid naming scheme can solve the isse (eg when using case insensitive names, the author of the naming scheme can decide how to handle clashes).

what cyclic imports issue was that again? the naming scheme instance can be passed as argument to this function from wherever it is called (or something like that).