Fix issue 32257

[ihorvansach]

Description (*)

This pull request fixes the issue #32257 related to Translate Inline.

Fixed Issues (if relevant)

1. Fixes Translate Inline does not work on second translate #32257

Manual testing scenarios (*)

See #32257

Questions or comments

The difference that in Magento2.4.2 when enable Translate inline e.g. Add to cart button (other elements too) start looking as

<button type="button"
                            title="{{{Add to Cart2}}{{Add to Cart2}}{{Add to Cart2}}{{Add to Cart}}{{themeMagento/luma}}}"
                            class="action tocart primary">
                        <span>{{{Add to Cart2}}{{Add to Cart2}}{{Add to Cart2}}{{Add to Cart}}{{themeMagento/luma}}}</span>
                    </button>

And e.g. in previus Magento2.3.3 it was

<button type="button"
                            title="{{{Add to Cart2}}{{Add to Cart2}}{{Add to Cart}}{{themeMagento/luma}}}"
                            class="action tocart primary">
                        <span>{{{Add to Cart2}}{{Add to Cart2}}{{Add to Cart}}{{themeMagento/luma}}}</span>
                    </button>

And this is related to additional renderer in \Magento\Framework\Phrase\RendererInterface\Composite::render(), previously there was 3 renders:
Magento\Framework\Phrase\Renderer\Translate
Magento\Framework\Phrase\Renderer\Placeholde
Magento\Framework\Phrase\Renderer\Inline

And new renderer Magento\Framework\Phrase\Renderer\MessageFormatter was added and that leads to additional {{}} element, so need to change REGEXP_TOKEN

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)

[m2-assistant]

Hi @ihorvansach. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[mrtuvn]

CC: @navarr

[ihorvansach]

@magento run all tests