[Content Bug] Update VPC page

[billy-the-fish]

hi folks :wave::skin-tone-2: I had a case with a customer recently, and they requested that the docs be updated. We only support one subnet/CIDR per VPC, but the docs don't talk about that anywhere. details are in this thread here: https://iobeam.slack.com/archives/CRT2F21B9/p1716312165948699?thread_ts=1715105056.116719&cid=CRT2F21B9 but I'm honestly not sure how best to distill the info on that thread. I think it should at the very least be a disclaimer. :pray::skin-tone-2:

valguz The customer ended up consolidating their subnets into the primary range of the VPC and connections from the various subnets/AZs are now working... he requests this scenario is clearly stated in the docs since it was so hard to diagnose and find a workaround. I'm not sure what the best way to do that is. @Dodd do you have any input on how we could document this more clearly? I don't think we have any information about this in our docs. I'm thinking some kind of disclaimer here? https://docs.timescale.com/use-timescale/latest/vpc/#complete-the-vpc-connection-in-aws