Long running soaking test for memory leaks

[sethAmazon]

We have no long running tests that can check for memory leaks.

I was think we just have a job that deploys the binary onto permanent ec2 instances. Add an alarm on the instance memory that will trigger if we are above a target.

Golang should not have memory leaks due to how it does gc. Though there could be a cache that is not properly cleared by collector code causing an issue.

[wyTrivail]

We used to use cwagent on the same instance to collect memory consumption of otcollector process as part of soaking test and perf test, not sure if this was removed afterwards?