TorConnect and TorSettings are initialized twice

A cypherpunk noticed that my tor-launcher changes made it so that TorConnect.init() and TorSettings.init() are called both in toolkit/components/tor-launcher/TorStartupService.jsm and before returning the object they create.

I think we should keep only the ones in TorStartupService.jsm.

This solves also the "Attempted invalid state transition from Configuring to Configuring" problem.