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`...
the issue is not wheter it is openended or not (because of suffixes). look at the `a` vs `aa` example. in this case `aa` is a candidate (`a` with suffix `a`), but need inspection of the module itself. so the naming scheme can return candidates, they still need inspection. (but it's the naming scheme that should return the candidates)