The XPCOM objects we currently have exposed to the DOM are actually going to be used as chrome classes. Remove them from DOM exposure for the time being while we figure out what the navigator.mozBluetooth DOM should actually look like.

Adding sort-of dependency since the patch in bug 730990 is getting backed out due to wrong review chain. Will need to land again here as simple XPCOM.

Due to the need to expose a BluetoothSocket object for implementing the file transfer profile in javascript, we'll actually be using DOM APIs for bluetooth in B2G v1 now, albeit protected by preferences that only allow them to be accessed by certain applications. This new strategy negates the need to unDOMize things. We'll just have DOM peers reviewing the bluetooth stuff (most likely bent, who's been reviewing thus far).

Kyle, you will also need super reviews for the API.