Provide curated list of containers to run tasks

[slemeur]

Description

When running a tasks, the user is asked on which container to run the tasks while he has not idea of what are all the containers (especially those for plugins).

We should currate the list of containers where to execute the tasks to only the user's runtime ones and use a similar mechanism than for opening a terminal.

Update: behavior should be the same when select container dialog appears.

[vzhukovs]

@slemeur, we can't assign hotkey to switch display machine list, due to following flow. Hotkey assigns to specific command, command then executes code. With new terminal item this is easy to implement. There is a boolean flag which just switch displaying of elements. But with machine list for the exec commands its a bit tricky. Tricky in that way, that we first call run task menu item, task list may contains of not only che task type, but shell and exec. Then, when user pick che task, we show machine list. We can assign hotkey to show the list of machines and switch display, but we need to update the whole mechanism of displaying task list. Because theoretical, user can call hotkey from any place and machine list will be showing. I think it will be not obvious for the end user.

So I propose a bit different approach. At first step show to user non-tooling containers and display the option to show all containers.

[sunix]

@l0rd @vzhukovskii @vparfonov this is not part of the endgame anymore right ?

[vzhukovs]

@sunix this issue is not mentioned in endgame plan

[slemeur]

@vzhukovskii : How the issue is related to hotkeys? I think you are mis-interpreting the description.

Also, I'd like to understand why this issue has been added to the sprint, while it's not part of the endgame and we have a busy list of other issues to address...
cc @vparfonov @l0rd

[vzhukovs]

How the issue is related to hotkeys?

and use a similar mechanism than for opening a terminal

In opening terminal when user opens machine picker he can see only user runtimes and after pressing the hotkey, he can observe all containers. So I've tried to align the same mechanism and for the task execution part.

I think you are mis-interpreting the description.

It's not a problem to update the behavior. Should we display the only user's runtimes and not display plugin containers?

[vzhukovs]

I propose such flow to display containers. There is the same flow to separate user developer containers and tooling containers. The same flow is used when user call action Find command:

When Find command is executed:

When new terminal opens:

When new task starts:

[vparfonov]

@slemeur Please take a look

[slemeur]

Good for me!