Fix i18n parser to enable the use of keys instead of value as key

By default i18n parser creates the english locales/en/plugin__camel-openshift-console-plugin.json file using the value as key. While it works for most case, it is not ideal for long texts containing html tags.

See doc: https://react.i18next.com/latest/usetranslation-hook

Start by locating the i18n parser configuration that generates locales/en/plugin__camel-openshift-console-plugin.json, then read the linked react-i18next useTranslation documentation. Define how keys should be selected instead of translation values, and verify that generated entries use stable keys rather than long HTML-containing text.

Written by the indexing model from the issue text.