Public probes: Add monitoring for inter-AWS traffic

[peterschretlen]

This is not an agent issue but rather a consideration for public probes. For visibility I wanted to create this in a public facing repo.

Our public probes all run out of AWS at the moment. When probing other services that run within AWS - not uncommon - network traffic is not routed over the public internet but rather goes internally via AWS’s backbone.

This issue is to track adding monitoring of intra-AWS traffic so we can better detect and inform on issues specifically affecting users monitoring services running in AWS. For example we could extend per-region monitoring to include probing and tracerouting AWS targets.