Case A. Context module has no local task to manage translations (and other local tasks too) on context detail page (edit page).
It is hard to follow every time this administration journey:
Administration > Configuration > Regional and language > Configuration translation > Context > "My Context" > Translate
Case B. Context module has hardcoded entity operations in context/modules/context_ui/src/ContextListBuilder.php
and it means that Config translation module can't extend entity operations to provide Translate link in actions dropdown on contexts overview page.
Case A.
Install Context, Config translation modules. Add some languages, add new context.
On context edit page there is no "Translate context" local task
Case B.
Same as in the above but follow contexts overview page.
Check that there is no action link to translate specific context
To cover case A.
Provide default local task and then config_translation module will do rest of the work for us.
To address case B.
Here it is an open question what's the best approach can be there.
I suggest do not modify ContextListBuilder class (to avoid adding a new dependency on moduleHandler service) and just alter this form to add a new action.
Create PR for case A,B. Discuss approach for case B and if any adjust it.
"Translate context" local task will be added on context detail page,
"Translate" action link (entity operation) will be added on context overview page.
4.0
User interface
Nice and simple solution. Works as expected, I think this can be merged. RTBC.