Selection Limitation with LocalizedTextField - Requires Workaround with Hidden LocalizedTextInput

**Description:**

The current implementation appears to have a limitation where selecting or focusing the localized text input functionality is not directly available within the `LocalizedTextField` component. This contrasts with the `LocalizedTextInput` component, which seems to offer this capability (as indicated by functions like `getId` and `getName` in its documentation).


As a result of this limitation, consumers are forced to implement a workaround to achieve the desired selection behavior. This workaround involves rendering a `LocalizedTextInput` component and visually hiding it using `AccessibleHidden` (as demonstrated in [this example](https://github.com/commercetools/merchant-center-frontend/pull/18751/files#diff-0cb5f3e36c993bd30df47fadb2a5dc3b1fce85f9c6924e77de0e29dbabae9854L224-R252)). This adds unnecessary complexity to the component usage.

**Expected Behavior:**

Ideally, the `LocalizedTextField` component should provide a similar mechanism for selecting or focusing the localized text input fields as the `LocalizedTextInput` component, without requiring the use of a hidden component as a workaround.

**Current Behavior:**

The `LocalizedTextField` component lacks the necessary functionality (or has a different implementation) for programmatically selecting or focusing the input fields for different locales. This forces developers to use the aforementioned workaround.