Fast-fail packets for remote servers that were received in a few seconds
If a client sends thousands of packets to a remote server that is not connected then Openfire will attempt to connect to the remote server for each packet. This will be a spike in the CPU. Instead we can just wait like 5 seconds before attempting another s2s connection. In the mean time we should treat queued packets as failed-to-be-delivered.