Closes #5640: fix translatePress compatibility

[Miraeld]

Description

I've done some refactor to improve the code. And also I've implemented the fixes requested.

Fixes #5640

Type of change

• Enhancement (non-breaking change which improves an existing functionality).

Is the solution different from the one proposed during the grooming?

No

Checklists

Generic development checklist

• My code follows the style guidelines of this project, with adapted comments and without new warnings.
• I have added unit and integration tests that prove my fix is effective or that my feature works.
• The CI passes locally with my changes (including unit tests, integration tests, linter).
• Any dependent changes have been merged and published in downstream modules.
• If applicable, I have made corresponding changes to the documentation. Provide a link to the documentation.

Test summary

• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I validated all Acceptance Criteria of the related issues. (If applicable, provide proof).
• I validated all test plan the QA Review asked me to.

[Mai-Saad]

@Miraeld Thanks for the PR. Can still see the 400 error for home/fr on https://new.rocketlabsqa.ovh/ while permalinks with/without / . Can you please check 🙏

[CrochetFeve0251]

@MathieuLamiot for it looks like the code is not working on the call we are fetching the response from the request.
My solution for this would be to add the status from the page (homepage or other ) inside the wp_wpr_rucss_used_css table.

Then we would just have to fetch that value from the table to know which queue we need to fetch the result from without having a bad JSON issue.

[MathieuLamiot]

@CrochetFeve0251 Sounds like a good approach to me 👍
Let's compute the is_home at submission time and store it for later use.

[Mai-Saad]

Closing this one in favour of #6266