Initial Testing

@ciaranevans I ran through to test today, hit a few bumps, had some open questions which will probably become a ticket each.

1. Dependencies, requires a working `cdk cli`, need link to install instructions. Also happened to hit a mismatch even though I installed recently, and had to upgrade.
```remote-workstation$ PIPENV_DOTENV_LOCATION=.env pipenv run cdk ls
Loading .env environment variables...
This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version.
(Cloud assembly schema version mismatch: Maximum schema version supported is 6.0.0, but found 7.0.0)
```

2. How does it know what aws account to use?
```
❌ remote-workstation-alex-station failed: Error: Unable to resolve AWS account to use. It must be either configured when you define your CDK or through the environment
Unable to resolve AWS account to use. It must be either configured when you define your CDK or through the environment
```
We should support `--profile` on cdk deploy, or add to the ENV. Workaround is to note that [default] is used.

3. What exactly does cdk destroy do? Should have clear instructions how to turn off remote instance, and what that means. Since it's Fargate on ECS, I assume once you turn it off, it's gone.

4. How to avoid issue with IP address allocation, "Best Practices" in instance management.
```
The maximum number of addresses has been reached. (Service: AmazonEC2; Status Code: 400; Error Code: AddressLimitExceeded;
```
## Wishlist

* Reminder to open a ticket about supporting TAGs for billing tracking.
* Option to use an existing Docker in ECR.
* Local config, maybe yaml or env to control instance size
* Opening port 22 to the machine that is deploying with a security group.