Standardize the module test workflow names

[tefirman]

Currently, the naming convention of the overarching test workflows for WILDS WDL Modules is mostly uniform, but not entirely. A lot of them go by [toolname]_example (e.g. gatk_example), but again, not all of them. After talking with @sckott , I'm wondering if we should just name the workflow the same name as the module in snake case, i.e. ww-gatk has a test workflow of ww_gatk. Whatever the pattern ends up as, it needs to be uniform across modules.

[sckott]

Sounds good.

An alternative is to not do it and use something like I'm using in #130 grep '^workflow' "$$file" | awk '{print $$2}' which extracts the workflow name. I'm not saying this is the right route - ideally there'd be a tool that could parse and pull out any part of a WDL file, but I don't know of any. Do you?