Allow HandleTranslations to be imported in any order

[antonioribeiro]

Summary

This line of code forces us to use HandleTranslations; in a order that doesn't affects the translations keys, because, if you load it after some other trait that adds things to the translations array it will be cleared and coming to the form lost.

Describe the solution you'd like

Ideally this unset() should go away. Is there a better way to ensure there will be no "strange" keys to HandleTranslations here?

Additional context

Found this because I had use HandleMetadata (which adds a lot of stuff to the translations array) loaded before it.