test: update new test cases and uuids

[vaeng]

The new tests ask for some kind of error for invalid codons.

Currently there example does not cover that aspect.
Should we skip these tests, or change the example?

I would vote to add error handling, but we do have some exercises with error handling already, so I would be fine if we skip the tests in question.

[github-actions]

This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested.

If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos.

[no important files changed]

For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping @exercism/maintainers-admin in a comment. Thank you!