Load scripts into Chrome properly

No dynamically-evaluated JavaScript. Use chrome.* api methods instead.
Load css by injecting link into page, rather than usint content_scripts.

I'm not sure this was actually good for anything. I just have a feeling that the more stuff that the browser sees as being loaded normally, the more reliable behavior and debugging we can expect.
Packaged jqueryui and angularjs internall; generate FF config dynamically (incomplete).

The firefox build does not produce a working extension now.
Stupid attempt to fix the stupid Goko load timing problem.

Goko's load process is so fragile that the #how-to-play element can get used before it is initialized. This is definitely a race condition, so no promises about reproducing it exactly, but it happens consistently on my machine in Firefox if I give the browser any real work to do at the DOMContentLoaded event.

I added a brief interval (100ms) to prevent this from happening, but this is certainly not a complete solution. I expect that some users will run into the same problem anyway.

I could add a longer interval, but that results in the avatars.js module not loading correctly. That module alters code in FS.Templates.Launch screen that only gets read on initialization. So unless that change happens quickly enough, the avatars module has no effect.
Start handling log+ sidebar in an MVC-friendly way.
Merge branch 'master' into chrome-nowrap

Conflicts:
	config.rb
	src/config/firefox/content/main.js
Use internal versions of angularjs and jqueryui
Merge branch 'chrome-nowrap' into logviewer-overhaul

Conflicts:
	config.rb
Finished logviewer overhaul:

created and fixed CSS for log viewer and vp counter
finished implementing shorted vp toggle text
simplified vp counter code
shortened dependency wait periods to 100ms