go/adbc/driver/flightsql: cache negative connection attempts

Flight lets a server return multiple addresses to try. We currently try each of them in turn every time. We should also cache failed addresses somehow such that if we have a list of locations and we know some of them fail and some of them work, we go immediately to using the working address; if the working address fails, then we can try the rest of the addresses again. This avoids a lot of time spent just sitting and waiting for connection attempts.