fix: do not sort the google translate results

[azu]

Fix unnatural translation order when the text is wrapped tag like <b> or <a>

Pros

• Fix unnatural order in some language

Cons

• This PR insert may translated text to a different node from the original node
  • Google Translate copy the style from the original node
  • This PR append rest results to the last node

Request:
<a i=0>TranslateWebPages is created by </a><a i=1><b>FilipePS</b></a>
Response:
<a i=1>TranslateWebPagesはFilipePS</a><a i=0>によって作成され</a><a i=1>ます</a>

Google translation result:

<a i=1> will be <b> because original node style is <b>

<b>TranslateWebPagesはFilipePS</b>によって作成され<b>ます</b>

This PR result:

The original text has 2 <a i=x>, but the translated result has 3 <a i=x>.

TranslateWebPagesはFilipePS<b>によって作成されます</b>

TranslateWebPagesはFilipePS | <b>[によって作成され, ます].join(" ")</b>

I felt that both are unnatural, I have no opinion.

fix #163

[FilipePS]

I see 2 problems with this approach:

1. The links are with text that does not belong to you, as well as bold text, etc. ... Translate this.
2. Adding the rest of the text to the last node makes it have a lot more text than it should. I can easily imagine a layout break on some sites, maybe even make the node disappear.

I consider adding this, but it would be something optional, which would be activated in the settings.

I already tried to implement an algorithm similar to the one used in chrome (which inverts the position of nodes, and even creates new ones). However, no implementation was successful.

[azu]

Yes, The design(style) will be broken on some websites.
This approach will be a good result on text content websites like a news site or blog.
I prefer that correct translation to the correct website's design.

I consider adding this, but it would be something optional, which would be activated in the settings.

I agree. It may be option.