[eks deploy] Configurable rolling deployment for controlled roll out

The current approach with "kubergrunt eks deploy" causes downtime due to the fact that all nodes in a group receive drain simultaneously and all replicas of affected apps (the same for ingress controller, stateful sets, etc) start migration in the same time.
Need to improve the update procedure to avoid downtimes.

Start with the `kubergrunt eks deploy` entry point and inspect the current node-drain and replica migration procedure. Define how a controlled rolling deployment should sequence node updates while avoiding downtime for ingress controllers, stateful sets, and other affected applications; done means the deployment no longer drains all nodes simultaneously.

Written by the indexing model from the issue text.