update adb's use of nsIDOMTCPSocket to work with recent Nightly builds

@ochameau: this is what I have so far, and it finds devices just fine (modulo other issues like #460), but push to device fails:

```
info: r2d2b2g: adb: pushing /Users/myk/Library/Caches/TemporaryItems/b2g/68bc7877-2192-854c-a47c-daebcff7e3f0/manifest.webapp -> /data/local/tmp/b2g/68bc7877-2192-854c-a47c-daebcff7e3f0/manifest.webapp
info: r2d2b2g: adb: /Users/myk/Library/Caches/TemporaryItems/b2g/68bc7877-2192-854c-a47c-daebcff7e3f0/manifest.webapp size is 669
info: r2d2b2g: adb: push onopen
info: r2d2b2g: adb: runFSM start
info: r2d2b2g: adb: runFSM send-transport
info: r2d2b2g: adb: push ondata
info: r2d2b2g: adb: runFSM wait-transport
info: r2d2b2g: adb: transport: OK
info: r2d2b2g: adb: runFSM send-sync
info: r2d2b2g: adb: push ondata
info: r2d2b2g: adb: runFSM wait-sync
info: r2d2b2g: adb: sync: OK
info: r2d2b2g: adb: runFSM send-send
info: r2d2b2g: adb: len=4 53454e44 SEND
info: r2d2b2g: adb: len=4 4e000000 N...
info: r2d2b2g: adb: len=78 2f646174612f6c6f63616c2f746d702f6232672f /data/local/tmp/b2g/
info: r2d2b2g: adb: Sending 669 bytes
info: r2d2b2g: adb: len=4 44415441 DATA
info: r2d2b2g: adb: len=4 9d020000 ....
info: r2d2b2g: adb: len=669 7b0a2020226e616d65223a20224d796b7a696c6c {.  "name": "Mykzill
info: r2d2b2g: adb: push ondata
info: r2d2b2g: adb: runFSM wait-done
info: r2d2b2g: adb: Response: FAIL
info: r2d2b2g: adb: push shutdown
error: r2d2b2g: ADB.push manifest file error: BAD_RESPONSE
info: r2d2b2g: adb: push onclose
```