ec2-cargo redesign

[rukai]

ec2-cargo should handle sigint by cancelling in progress command and waiting for another prompt.

I spent some time using ec2-cargo today, I think I've taken the wrong approach with it.
Having an instance spun up that is then killed by sigint (ctrl-c) is reasonable, but we should really move to use remote editing instead of rsync.
vs code's remote editing is really quite excellent and hides latency well.

ec2-cargo should:

• spin up an instance and set it up for shotover dev.
• install bacon, lazygit + lazydocker
• Take a branch name to checkout.
• Dont fail if shotover failed to build.
• Provide ssh_instructions() at conclusion of setup.
• provide command to rsync back local for the purpose of pushing to github?
  • No other commands though, expect the user to ssh + vscode remote for all development
• Mention that ctrl-c will attempt to kill the EC2 instance but may not succeed.