[Issue] Initialize inline translations module only when they are enabled

[m2-assistant]

This issue is automatically created based on existing pull request: #27696: Initialize inline translations module only when they are enabled

---

Description (*)

This PR is a part of my effort to improve Magento 2 frontend performance.

The focus point of this PR was to remove downloading of inline translations JavaScript modules when they are not enabled. This was happening because they were defined in deps, which is completely redundant because they are properly initialized in https://github.com/krzksz/magento2/blob/98e04e174906799b941011a9fb1b5890a5e7cae9/app/code/Magento/Translation/view/frontend/templates/translate_inline.phtml#L57

While I was touching the files anyway I took the liberty to:

• Move escapeHTML to utilities (it is not used anywhere else and there is already an unescape counterpart).
• Fixed utilities dependency for serialize method.
• Simplify logic and variables in few places.

Performance improvement

Tested on Magento 2.4-develop with Luma and sample data.

• 207 → 203 JS requests (-1.93%).
• 794.39kB → 773.44kB JS transferred (-2.64%).

Manual testing scenarios (*)

1. When inline translations are disabled there is no request for translate-inline JS file.
2. When inline translations are enabled, they work as expected.

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #27696 by @krzksz in 2.4-develop branch
Related commit(s):

• 28d1af5276caa759139299096e0cbc40f4618da2
• b842083a7b6e08418f5bbb16f0a90abaf1bd8b44
• fe00511295cbd814f4a852729fbdc89dcc7fb4a6
• d64eaf403c059e306756b39f24a0645e3ef96cb4
• 1861c47cb029c1acf515e7605cb787ff2a1719f8
• d7305bc2bda776ff3eff2ddce9186c83a49f2c35
• 52432e5dff93fd23383ab1a8aa6409113b8e2d41
• d3c9a49cb051d8654826902c420ff47cdcc3279b
• 52cb062d8979f400b931e317a6da3880ec5d921c
• d2883edd660d86437dfb4f6b177ec9b57f9e33bb
• 217e993560cb2db16a76bf29797e649ca6d2d678
• 703add17b4fd31607fc6aa0ad3b0c41c72ec43b9
• cbc6cc0765d597e53b7821e78f108e767bdff9e9

The fix will be available with the upcoming 2.4.2 release.