Dry-run for editing or recreating containers

[anderbytes]

Is your feature request related to a problem? Please describe

My portainer is behind a reverse proxy, and even the management port is behind it (not exposed), making it a little more secure.
But... whenever I have to edit or recreate the container of the reverse proxy, it doesn't work (of course, as the portainer itself runs behind it).

Portainer goes unavailable, and I have to manually restart the reverse proxy container, that remains un-edited.

Describe the solution you'd like

It would be nice to, when importants commands are made (specially 'docker run'), that some 'dry-run' output allow us to get that operation command and run ourselves via ssh, which would then allow us to run it outside portainer for scenarios like that.

In other words, the "Deploy the Container" and the "Recreate" buttons should have a checkbox for "Dry-run: only show the resulting command"

Describe alternatives you've considered

I think it would be impossible to make some other kind of solution from 'inside' portainer, because the commands never 'go all the way' right after the reverse proxy container is stopped. Then red portainer pop-up errors appear.

Additional context

It would also be helpful for educational purposes, for us to learn more and understand what is happening inside the clockworks for each action of these.