Update String resources with new Transifex translations

[danesfeder]

Closes #888

We also had uploaded test app strings being used as keys, which are not translatable. I marked them as such here.

[Guardiola31337]

Comments lie... 👀 https://github.com/mapbox/mapbox-navigation-android/pull/889/files#diff-79501bd1c71d26dd2207bbd5af379e00L6

"Code never lies, comments sometimes do."
- Ron Jeffries pic.twitter.com/tXk0fXgN5Z

— The Practical Dev (@thepracticaldev) April 22, 2018

Let's remove them 🙏
IMO, they're not giving any value here, the string name reflects their purpose perfectly.

[1ec5]

Let's remove them 🙏
IMO, they're not giving any value here, the string name reflects their purpose perfectly.

I disagree, because the key is machine-readable, whereas the comment is human-readable. Transifex displays the comment prominently in the translation UI. The key is more obscure, and translators often have no clue what the key means out of context.

If the comments aren’t providing any value, then consider improving the comments to explain the differences between each feedback type and where the string appears in the UI. For example, is it a label on a button? Are there any length constraints? Should it be translated as a command (verb)?

[1ec5]

@danesfeder, remember to update localization.md to reflect these changes. Thanks! (This guide should also mention updating that document.)

[Guardiola31337]

Transifex displays the comment prominently in the translation UI. The key is more obscure, and translators often have no clue what the key means out of context.

Didn't know that Transifex displayed the comments somehow to translators (that's awesome 🎉).
As this is the case, yeah I agree, let's keep them and as @1ec5 mentioned let's try to update them so they provide the most value.