Builder.connect(): return the connection when it succeeds (check was inverted)

[SanniniciStyle]

Disclosure: this was found while building WatchSync with heavy AI assistance (Claude Code — "vibe coding", if you like). We work carefully: everything below was verified with the included unit test, but please review it with that in mind.

Both AdbConnection.Builder.connect() overloads have the check inverted:

if (adbConnection.connect()) {
    throw new IOException("Unable to establish a new connection.");
}
return adbConnection;

so a successful connection throws, and a failed one is returned. Now if (!...), and the failed connection is closed before throwing (it was leaked).

AdbConnectionBuilderTest connects to a minimal plain-text adbd on localhost that accepts at once:

Before: java.io.IOException: Unable to establish a new connection.  Tests run: 1, Failures: 1
After:  OK (1 test)