Do not run requestAnimationFrame when in extension

- I believe there is a bug in Windows where using a
  requestAnimationFrame loop inside a content_script causes a Chrome
  memory leak.  This is NOT a leak in the JS Heap.  This leak does
  not occur on Mac (OS X).

  Bug reference here:

  https://code.google.com/p/chromium/issues/detail?id=425236

- Running TakeOver plugin with this change results in a non-leaking
  version in both Mac and Windows
cleaning up logic for selecting background processor method
oops, forgot the soak on chrome object
Add ability to set Loop Type

- Allow user creating a ReconnectingWebSocket to set what kind of
  repeating loop they want to use
Remove requestAnimationFrame completely

- Use only setTimeout per request from Will B
Merge pull request #8 from glg/fix_reconnect_ws_leak

Fix reconnect ws leak