AN-186 Clean up pools from Google Batch enablement

[jgainerdewar]

This is a follow-on to #367 now that the non-prod pools there have been (mostly) put into use.

• Update test utils to use new pool version
• Remove the old versions of pools from pool_schema.yml files
• Remove ALL resource-config files for unused pools

Questions for reviewers:

• Do we want to remove resource-config files for older pools? Is this desirable cleanup or am I deleting a useful record?
• In AN-186 Add pool configs with Google Batch enabled #367 I added new versions of all non-TDR pools in environments I didn't know to be defunct (perf, alpha), because this change should apply to ALL new Terra workspace Google projects. In a couple cases, though, I couldn't find where the pool was used, so I couldn't update that usage to the new pool version. This leaves us with a newer pool with the correct settings, and an older pool that may or may not be in use somewhere, and so can't be removed. What's the best way to handle this? The two pools in this state are tools/cwb_ws_fiab_v7 and toolsalpha/resource_toolsalpha_v8.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[kevinmarete]

Looks is order, thanks for cleaning up!

[dvoet]

I can't find any reference to tools/cwb_ws_fiab_v7, or v8 for that matter. Maybe their use died with FIABs. The comment here says resource_toolsalpha is for local testing. Maybe you want another PR for it, but I think you can drop cwb_ws_fiab all together and drop the old version of resource_toolsalpha