NLB access across VPC peering has evolved since #611

[jpluscplusm]

Hey all 👋

#611 reflected the AWS docs at that point in time but, reviewing them today I can't see any indication on the linked AWS troubleshooting page that cross-VPC NLB connectivity/reachability is still a function of consumer instance type.

awsdocs/elb-network-load-balancers-user-guide@21dc1ff#diff-b3c41e866253fd714e911e5df66b9c58de3eb6c08200f09d8ccb8c2d050f47aaL18 changed the restriction from named instance types to "Nitro instances" ..

... and then awsdocs/elb-network-load-balancers-user-guide@7afdbe6#diff-3eab451a4033fc86129770b0699db9da9c4f69c700c8b3995a3a0355aff884afL7 changed the restriction to "VPC peers require ip-address targets, not instance-ids".