Ensure translation of context for PlutusV1-V3 fails for:

• - presence of ScriptHash in guardsTxBodyL (note that reqSignerHashesTxBody was there before and as such a list with just KeyHashes should not cause a failure)
• - presence of new RequireGuard native script case anywhere in a transaction We don't translate actual scripts to plutus, so this one is not necessary. Also if there is a RequireGuard case anywhere within a transaction that requires a script hash then GuardScriptHashesNotSupported above will be triggered. This point has an interesting use case that RequireGuard native scripts that only require a key hash can co-exist in the same transaction as PlutusV1-V3 scripts, which kind of makes sense, since semantically it becomes equivalent to RequireSignature

This ticket tracks the actual translation and imp spec tests for all of those cases

These two types of failure cases should be done either in two separate PRs, or at the very least two separate commits.