protein-translation: Implement canonical-data.json

[kytrinyx]

We want to have a standard set of test inputs and outputs for each exercise to
make it easier to port them to new languages, as well as to help keep the
exercises in sync.

The Protein Translation exercise can be found in the ./exercises/protein-translation/ directory.

The step-by-step instructions for how to compile a canonical-data.json file is
described in this section of the contributing guide.

See http://exercism.io/contribute/canonical-data/protein-translation for the up-to-date list of
language tracks that have an implementation of the Protein Translation exercise.

The tracking issue has more context.

[petertseng]

Here is a thing to consider for whoever takes this on:

As you will see in #268, we deprecated an exercise called nucleotide-codons in favour of protein-translation. Both these exercises deal with converting codons into protein names.

The exercises worked in slightly different ways, which I summarise but you can see the original analysis at exercism/rust#267 (comment).

• nucleotide-codons introduced in Add nucleotide-codons exercise #93 introduced the concept of compressions.
• protein-translation introduced in README for protein-translation #37 acts on multiple codons at once.

When creating the canonical data for this exercise, you should consider which of these two concepts to include.

[ErikSchierboom]

Closed by #997.