rpc: socket: Explicitly error if we exceed retry count
rpc: socket: Explicitly error if we exceed retry count

When we autolaunch libvirtd for session URIs, we spin in a retry
loop waiting for the daemon to start and the connect(2) to succeed.

However if we exceed the retry count, we don't explicitly raise an
error, which can yield a slew of different error messages elsewhere
in the code.

Explicitly raise the last connect(2) failure if we run out of retries.

crobinso/libvirt,andreabolognani/libvirt,libvirt/libvirt,fabianfreyer/libvirt,VenkatDatta/libvirt,eskultety/libvirt,libvirt/libvirt,fabianfreyer/libvirt,andreabolognani/libvirt,eskultety/libvirt,fabianfreyer/libvirt,jfehlig/libvirt,nertpinx/libvirt,crobinso/libvirt,VenkatDatta/libvirt,crobinso/libvirt,fabianfreyer/libvirt,rlaager/libvirt,eskultety/libvirt,crobinso/libvirt,jardasgit/libvirt,jardasgit/libvirt,jardasgit/libvirt,olafhering/libvirt,VenkatDatta/libvirt,nertpinx/libvirt,datto/libvirt,zippy2/libvirt,VenkatDatta/libvirt,jardasgit/libvirt,libvirt/libvirt,eskultety/libvirt,andreabolognani/libvirt,VenkatDatta/libvirt,olafhering/libvirt,zippy2/libvirt,eskultety/libvirt,nertpinx/libvirt,jardasgit/libvirt,taget/libvirt,taget/libvirt,rlaager/libvirt,rlaager/libvirt,taget/libvirt,olafhering/libvirt,andreabolognani/libvirt,rlaager/libvirt,jfehlig/libvirt,jfehlig/libvirt,datto/libvirt,zippy2/libvirt,taget/libvirt,datto/libvirt,fabianfreyer/libvirt,andreabolognani/libvirt,rlaager/libvirt,datto/libvirt,nertpinx/libvirt,jfehlig/libvirt,olafhering/libvirt,nertpinx/libvirt,datto/libvirt,libvirt/libvirt,taget/libvirt,zippy2/libvirt