[checks] wait for healthiness and termination (#16)

* [checks] add a status OK (healthiness) checker

Also removes extra minute of wait, inbetween EC2 start and SSM testing

* Use a terminateWaiter

* Log the AMI used for testing

* Log when we start terminating

* Log as we terminate

* Add some padding

* Wait 5m for healthiness (it takes 3m)

* Update docs

* fix syntax

[checks] improve ssm command invocation logging (#15)

There are scenarios where the SSM service is reachable, but, it's commands timeout.

[checks] make api-endpoint parameter optional & update usage docs (#14)

* Update docs to reflect api-endpoint is optional

* Make api-endpoint optional

[diagnose] test service connectivity when no VPC endpoint exists (#12)

* [.gitpod] add devcontainer.json and automations.yaml

* Fix

* Only require private DNS for execute-api, as per our docs

* [diagnose] test service connectivity when no VPC endpoint exists

This helps for when central VPC endpoints are used, which exist in a separate VPC (not the one you are testing from)

* Add execute-api service check for main subnet

* Fix binding for api-endpoint and instance-ami

* Do not provide a default

support custom AMI (#10)

* support custom AMI

* Apply suggestions from code review

Co-authored-by: Kyle Brennan <kyle@gitpod.io>

---------

Co-authored-by: Kyle Brennan <kyle@gitpod.io>

Fix support for me-central-1 & panic from private Gitpod network (#9)

* Fix panic on diagnose for private networks

* Introduce getPreferredInstanceType

The available types vary by region. T2 is the cheapest, but not always available. T3a is cheaper than T3 but uncommon. T3 more expensive, but available in most regions.

* Log the instance type selected

* Refactor

* Log input params

Tolerate https scheme & update docs (#8)

* Tolerate https scheme & update docs

Private networks may need to have the policy updated for VPC endpoints, otherwise gitpod-network-check will fail.

* Cleanup

Test `https-hosts` as part of `diagnose` (#7)

* Test `https-hosts` as part of `diagnose`

This helps customers test outbound HTTPS connectivity from the main subnet.

This helps assert connectivity (or not) for SSO and VCS integration

* update docs

Download latest binary & Add CODEOWNERS (#6)

* Download latest binary

* Add CODEOWNERS

* Check to enable private DNS in VPC endpoints

Merge pull request #5 from gitpod-io/kylos101/tolerate-duplicate-subnets

Tolerate two subnets and Introduce Cleanup command