Make diagnostic system aware of un-compiled modules

[MarkusPrim]

Currently the module diagnostic system is only aware of modules which are compiled. To make it aware of un-compiled modules this PR introduces a two-step procedure:

• Run a small python script to crawl all gambit bits from the source directory at the end of cmake (or any other time).
• Utilize the generated file to create a full list of gambit modules when using the diagnostic system, tagging them with ok or ditched/disabled.

This is the first of two PR related to Issue #61 . I thought it be best to create two simple PRs and discuss early. This PR alone also works perfectly fine standalone. The second PR will then tackle the issue of how the module/backend was removed from compilation, either if automatically disabled, or explicitly ditched.

[tegonzalo]

Not much to comment here, but just a general comment. You said that the second part of the PR would resolve when a module has been ditched or disabled. I'm not sure what you mean about disabled here, as modules are always part of the compilation unless they are ditched. If I am correct then you should just change line 63 of diagnostics.cpp to say ditched and that will be all.

[MarkusPrim]

Good point, I will change that. However the same does not apply for backends for example, and on that the comment about ditched/disabled was based.

[MarkusPrim]

@tegonzalo I incorporated your comments and will merge after the successful build.

[pstoecker]

I have just tested ./gambit modules on CosmoBit_development which is up-to date with master and includes the modifications of this PR.

I have seen that ScannerBit is listed as ditched even though it is clearly there -- otherwise good look with scanning 😄 . I am not sure whether it only occurs to me, but this seems to be a small bug or easter egg.