Editor experience: translation context

### Describe the problem

When translating, I'd like to be presented with consistent and stable, not disappearing list of strings in a a component; or have an option to be presented with it.

Currently the role of the translation context has the Nearby strings tab. Though it has the same placement and level as four other tabs connected with editing, and easily disappears.

I see a value in being able to see both Nearby strings and Automatic suggestions at once, to confront a suggestion with an existing translation in context. Being able to see the translations helps to be consistent in translation.

Being able to scroll through entries to jump further – either to lookup an already translated text or to skip to some next not-direct-sibling-fragment I'd like to translate – would be a quality of life improvement.

### Solution brainstorm

Pulling the Nearby strings to the left, and making it actually a scrollable list of component entries would solve my concern, I think.

It would be a bit problematic for language-level translations (in contrast to component-level ones) and custom searches or custom ordering, what to present there. Maybe for those cases it could be “downgraded” back to Nearby strings tab? Or gray out entires highlighting only those that match the filtering?

### Describe alternatives you have considered

Alternative is using split desktop with a component browse view in a separate browser window. A huge disadvantage of it is the lack of interactivity between the windows.

### Screenshots

### Additional context

Much of other translation software use this pattern. I think it's due to its usability. It includes Transifex, Crowdin, Pontoon and Lokalise (I've just created an account there to satisfy my curiosity :) ).

Most likely it's obvious, but for completeness I will mention that the infinite scroll pattern would be a good fit for the implementation on the frontend part, as far as I'm concerned.

Thank you!