Add alternate deployment strategy (remove-before-deploy)

[yamalight]

Currently, exoframe will build and deploy new container and remove the old one only after new one is up and running.
This works fine for majority of services, but some require removal of old container before starting the new one (e.g. telegram bots that can only have one connection to API).
We need to introduce new config property (e.g. deploymentStrategy?) that can be either default (or removeAfterDeploy) or removeBeforeDeploy.
Should be fairly trivial to implement.

[dualizeo]

Doesn't Watchtower do this?

[yamalight]

@dualizeo how would that help in updating project deployed with exoframe? 🤔