Ab#133293 enable translation pages widgets title

[GhaziAlibi]

Description

This pull request implements multi-language translation support (English en, French fr, Ukrainian uk) for page names, workflow names, dashboards, and all widget types (Grid, Chart, Map, Summary Card, and Text/HTML Editor). It also fixes inline change-detection saving logic for page/workflow/dashboard titles and cleans up the UI/layout styling in the settings dialogs.

Useful links

• Ticket: AB#133293

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (refactor or addition to existing functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

The changes were verified using both manual UI validation and automated test suites:

• UI Verification:
  1. Opened settings dialogs for Grid, Chart, Map, Summary Card, and HTML Editor widgets; verified that the language tabs (EN, FR, UK) render correctly without styling issues/empty margins.
  2. Edited title fields for non-active languages (e.g., French and Ukrainian) and verified that the save button correctly triggers the GraphQL update mutation to the backend database.
  3. Verified that the translated titles render correctly on both Back-Office and Front-Office preview layouts based on the active language.
• Unit Tests:
  • Ran npm run test (npx nx run-many --target=test --projects=ui,shared --configuration=ci) to ensure all component and pipe specs pass locally.

Screenshots

Screencast_20260610_022127.webm

Checklist:

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-backend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules