Seems like we're getting more and more false positives from customers that are caused by our logs. We need to "civilize" them again on various levels.

1. We need to get rid of pyroute2 deprecation warning in kuryr-cni.
2. Flask logs of 200 /metrics calls are spamming the logs on INFO level, that's awful.
3. `WARNING urllib3.connectionpool [-] Connection pool is full, discarding connection: <openstack-API>: queue.Full` - that's a common false positive, we need to solve or suppress it because it's harmless.
4. If LB is stuck in `PENDING_UPDATE` state we need to clearly log that it's Octavia fault and not some ambiguous `ResourceNotReady`.
5. If we time out waiting for port to become `ACTIVE` we need to say that it's Neutron fault on CNI side. It'd best to make sure we return error string to CNI and that'll be shown in `oc describe pod`.
6. We still do awful job on signalling what caused a healthcheck to fail. Clear reason should appear in both `oc describe` and logs.