Gherkin GLV translation failure then error is thrown on step construction

Due to the need to compile traversals before translating them in `generate.groovy` for GLV-specific traversals in Gherkin tests, we cannot test failure path for steps that throw on constructions, because the traversal translation will fail (e.g. range step). 

The easy work around is to add static translations for those tests, but they will not scale.