Compose Restart inconsistency

Hi,

the restart commands in the context menus behave inconsistent.

The restart command in the context menu of a compose file in the Explorer View will do an docker compose down followed by an docker compose up

The restart action on the context menu in the docker panel when selecting a stack will do a docker compose restart.

Could we change that to doing only a restart in both cases and add a recreation command that does the down up cycle?

For context, we have a stack of test-dbs without mount, so to reset the data down and up is enough. But we start it by default with a different name than the default compose name. But the restart command in the Explorer View will not work, as it will take the default name for the stack. And the restart in docker panel will not work as a normal restart will not recreate the container.

Trace the Compose actions exposed by the Explorer View and Docker panel context menus, then compare how each invokes Docker Compose. Make both restart actions use restart semantics and add a separate recreation action for the down/up cycle, preserving the stack name; verify both menus expose the intended behavior.