[feature/test-watchdog-rewrite]

[Cameronsplaze]

The rewrite was successful! The architecture is more simple, cheaper, and supports more container types now. The only downside vs the old system is SSH by itself probably isn't enough traffic to keep the container up, but you can just get around this by connecting the container's client on-top of ssh-ing in.

Description

Removed a lambda w/ pushing custom metrics. Switched to using ec2's built in "traffic in" metric. Only check "in", because "out" is too noisy, and is pointless in determining if people are connected or not. Just telemetry can throw it off. If traffic is coming in though, either someone is connected, or the container is downloading an update. Either way, you want to stay on.

Motivation and Context

The architecture is more simple, cheaper, and supports more container types now.
Fixes:

• [Optimization] Look into if it's worth switching some/most of watchdog to use ec2 networking metrics #21
• [Feature] Support GeyserMC if possible (Edit Watchdog: Minecraft Bedrock Clients connect to Java Server) #70
  Unblocks:
• [Bug] How to deal with container crashing on startup. #73

How has this been tested?

Deployed all 3 current examples, and make sure they had thresholds that would work.

Screenshots (if appropriate):

N/A

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• All new and existing tests passed.
  • I have added tests to cover my changes.