Fix debugging extension

[GoogleCodeExporter]

- Build extension during the regular build and emit it to bin/extension along 
with the pem that was used/generated and the update manifest.
- During the dist copy it to the static folder so that the crx can be served up 
by the collide instance.
- Change the installation URL for clients that do not have the extension 
installed to point to the locally served install location.
- Have the extension maintain its own internal whitelist of sites it allows to 
connect to it. This means the global content script needs a lenient whitelist 
in the manifest JSON since we can't know ahead of time the hostnames for the 
collide servers.
- Make this whitelist allow localhost by default and be configurable via the 
extensions settings page.

Original issue reported on code.google.com by jaime...@gmail.com on 4 Jul 2012 at 11:01

[GoogleCodeExporter]

Sweet, I was about to enter this. :)

Original comment by dragonsinth on 5 Jul 2012 at 6:27

[GoogleCodeExporter]

I was playing around with this and noticed that the debug extension was 
missing. How do I compile the debug extension for installation?

Original comment by kdiet...@gmail.com on 1 Oct 2012 at 5:19

[GoogleCodeExporter]

The extension is actually present in source code. If you want to play around 
with it, you can load it as an unpacked extension (and it works) from:
<repo>/java/com/google/collide/extensions/chrome

So far the main cool this it does (in addition to JS debugging) is auto-reload 
CSS as you type. The one caveat being the CSS file must be referenced as an 
href via a <link> tag.

Original comment by jaime...@gmail.com on 1 Oct 2012 at 3:25