feat: translate layout in advanced editor

[GauBen]

Working on the premises of https://github.com/Jahia/content-versioning/issues/8: the translation layout is now part of the advanced edition layout

The two columns were swapped

It should be somewhat easy to add new options (e.g. content versioning) next to edit/translate/advanced options

[github-actions]

🦜 Chachalog

No changelog entries detected. Learn more about Chachalog.

Create a new entry online or run npx chachalog@0.5.2 prompt to create a new entry locally.

[GauBen]

The tests are failing, I don't know why, I don't know how to run them locally to save time

[GauBen]

@copilot look at the test failures and fix them

[Copilot]

@copilot look at the test failures and fix them

Fixed in a6bb3430. The regression was that normal edit actions were still receiving translate side-by-side context, which could put the editor into the wrong mode. I scoped that context back to the translate action only, then re-ran yarn lint and yarn test locally successfully.

[GauBen]

@copilot Look at the CI integration tests and fix them

[Copilot]

@copilot Look at the CI integration tests and fix them

Fixed in 1fa11ef1. I traced the integration failures to fullscreen tab state not being persisted: after switching tabs/languages, regular edit screens could still inherit translate mode behavior. The fix persists the selected fullscreen tab in editor config and only applies translate-specific read-only/publication logic when the active tab is actually Translate. I re-ran yarn lint, yarn test, and the final validation (CodeQL clean).

[jahia-sonarqube]

Quality Gate failed

Failed conditions
7.7% Duplication on New Code (required ≤ 3%)
13 New Maintainability Issues (required ≤ 0)
5 New Reliability Issues (required ≤ 0)
48 Added Technical Debt (required ≤ 0)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube