Isolate WDL's to `cromwellapi` tests

[tefirman]

We need the ability to isolate a particular WDL Unit Test to the tests described in cromwellapi and not have them run in the cromwelljava test runs.

For example, helloModuleHostname and gpuAlloc are PROOF-specific tests of the module and gpu runtime attributes respectively. So when they're run via the PROOF API, they complete successfully, but when they're run locally via Cromwell, they fail due to the unrecognized runtime parameter.

If we can specify somehow to not run these WDL's in cromwelljava , then these two WDL's can be merged into main pretty much immediately after.

[tefirman]

After some Lakeside Chat discussion with @sckott , a good option for implementing this would be an additional conditions.json file that describes the unit test expectations. For example:

{
    "badVal": False,
    "badRunJava": True,
    "badRunAPI": False
}

If the json isn't provided, we can assume by default that it's expected to pass both validation/test run everywhere. My guess is that it would be easiest to incorporate this check in the pytest scripts rather than the GHA yml files.

This could also be used to eliminate the badVal/badRun naming hack that's currently in the infrastructure, I know that's less than ideal.

[sckott]

I like it. Having one place within each WDL folder that gives the python test code a place to look is nice and clean I think