Revert new feature to keep LocaleString fields open or make it optional for the users

Who would benefit?

PIM Users

What impact would it make?

We had two different customers reaching out to us when the feature to keep LocaleString open on the last edited language was implemented, because they thought it was a bug. For example one of the customers enriched the wrong language of a new entity, since LocaleStrings are now kept open with the latest edited language selected instead of being set back to main language when you change for a new entity. Please revert this change as it does not help the customers or at least make it optional to allow the customer to adjust the function to suit their specific work process.

How should it work?

If not reverted, it can for example be a check-box, like Hide read-only that each user can check or kept unchecked, whichever suits them best.

Why is it needed?

To allow our customers to keep their current work process.