Android test262: Mac client can now receive and display echoed log messages from the device as it is running via a socket connection.

The system reuses the initial port communication for the http server to denote it wants a log stream event instead of an download. From there, the socket is kept open to echo messages through the socket back to the Mac client.

The Mac client opens a new window for each device and displays the log messages in a NSTextView.

Also added Alert dialogs for resolve/connection errors.
Android test262: Modified CocoaHTTPServer to workaround problem that the connection class is created behind the scenes and you can't get access to it which prevents clean ways to access outside GUI.

This is a known problem:
http://stackoverflow.com/questions/8492002/add-run-time-information-to-cocoahttpserver-using-custom-response-class
https://github.com/robbiehanson/CocoaHTTPServer/issues/5

My technique uses a block callback to give you a hook into the creation process.
Android test262: Started moving download progress UI into LogStreamWindowController to better handle multiple instance situations.
Android test262: Bug fixes for download mode (null pointer) and echoing memory events. Enhancements to Mac client: better handling on per-device basis; download progress moved out of main window. Added a clear window button.

Resolve is now re-run with every new connection attempt. Old log streams are attempted to be shutdown and replaced with the new one.

Two problems with stream mode:
1) Autoscrolling causes performance make app unresponsive around 50,000 lines. (autoscrolling is now commented out)
2) Cocoa raises an exception for large append strings to textviews and halts the program. (I’m not sure where. Somewhere between 150,000 to 900,000 lines.)