Review duplicated QuantBook system handler initialization

[Martin-Molinero]

Expected Behavior

• ideally we don't recreate system handlers twice from the start

Actual Behavior

• start.py (for python) and QuantConnect.csx (for C#) start the system handlers, but later QuantBook constructor is clearing the composer and recreating them. This causes some pain points when using IB as a data provider for example, since it triggers twice it's initialization

Potential Solution

N/A

Reproducing the Problem

• Start jupyter notebook, create quantbook object

System Information

N/A

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that this is not a duplicate issue by searching issues

• I have provided detailed steps to reproduce the issue