Do not reload accounts when initially setting the application proxy
This is quite the sneaky issue, but I think it goes like this:
- NetworkController is initialized by the QML engine and it's constructor is called
- setApplicationProxy is called within said constructor
- AccountManager's reloadAccounts is called, which in turn emits accountsReloaded
- accountsReloaded can trigger some signal handler in QML, in turn making the QML engine initialize NetworkController again
Now setApplicationProxy has an optional parameter used by NetworkController's constructor to prevent this situation from happening in the first place.