Use HTML translation feature including inline tag movement about firefox-translations

[andrenatal]

The team has very little confidence in the current bergamot-translator's embedded HTML translation capabilities due the very well documented issues and long time it took to have it implemented along the constant belittling displayed from your team in regards to the way we were trying to solve this problem while your team was still unable to provide the right tools (again also well documented).

But we decided to give it another try in a couple weeks and submit it to QA, but if we still have issues like page defacing, stripping of tags and etc, we will abandon this altogether and remain with textNodes which will be the approach utilized in the user test we are mandated to run internally.

[abhi-agg]

#111 imported the latest API changes in bergamot-translator which will enable the extension to use HTML translation feature.

Now, the extension needs to parse the content to be translated and send a boolean flag to indicate whether the content is html or not per batch item to get the translations.

[jelmervdl]

Now, the extension needs to parse the content to be translated

The extension (developer) knows whether it is translating Node.textContent, Node.value or Node.innerHTML if I'm correct. I don't think there is ever a need for parsing the content to determine this flag's value.

[andrenatal]

Fixed by #127