Use translation selector for localized inputs

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.4.3.6 CE GA6, 7.4.13 DXP U2, 7.4.3.7 CE GA7, 7.4.13 DXP U3, Master
• Component/s: DXP Components Web > Translation Manager
• Labels:
  • fi-s-new-team
  • liferay-update-dxp-3-7413
• Epic/Theme:
  • transla
• Fix Priority: 3
• Epic Link: Translation Manager UX improvements
• Sprint: S04E30 - Sea Change
• Git Pull Request: https://github.com/liferay-echo/liferay-portal/pull/6794

Description

Use the translation selector variant for localized inputs instead of the Translation Manager (from now TM) default variant. 

Context

The TM is a component with 3 variants designed to be used in different cases.

From the definition document:

"The TM component must be used only once on a page, often being placed on top of the page. The main reason to have just one component per page is to focus user attention on the feature to manage the translations for that content."

Thus, the TM default variant (the one that provides the "Manage Translations" action) must be used only one time per page. 

This was the initial idea of the Lexicon team about the usage of the component. However, we didn't study in deep to provide the feature of managing the translations from every localized component on the page.

Thus, this bug has to be discussed and agreed upon by the product manager of the team.

Steps to reproduce

1. Go to Web Content > Structures
2. Create a new structure
3. Select Properties tab
4. Click the Language button close to the description field
5. Click the Language button close to the title field

Current state

Desired state
Use the translation selector for localized inputs