Fix connector switching hangs with Firefox 3.6 on Windows

[simon]

Right now, if the user opens Standalone after opening Firefox 3.6, we are hanging Standalone startup and hanging Firefox 3.6 on shutdown, because Firefox 3.6 can receive a releaseLock command, but it can't send a lockReleased command. We can ignore the releaseLock command, but Standalone will still hang expecting a lockReleased command. At the very least, we want Standalone to display an error message. Our options are:

1. Have standalone wait a fixed amount of time for a response after requesting that the DB lock be released before erroring out and closing (or, alternatively, before trying to open the DB again)
2. Implement the connector switching messages with the almost entirely undocumented version of js-ctypes that came with Firefox 3.6
3. Find a way to get the version of the running Firefox process using ctypes from within Standalone
4. Some kind of trick involving passing the ZoteroIPC command line option with nsIProcess
5. Drop support for Firefox 3.6 on Windows entirely

I think I am going to implement option 1, since it seems like a good idea anyway. If this isn't sufficient, I'll revisit this.

[simon]

In [9729]:

Fixes #1844, Fix connector switching hangs with Firefox 3.6 on Windows. Standalone will just take an extra 5 seconds to start if started while Firefox 3.6 is running.