Fix for command line arguments handling

Problem

When running on Awake and passing arguments via the command line, these values are not applied, the default settings are used instead.

Root Cause

The logic inside the SignalingManager’s Awake() function creates a signaling object that is passed to the _Run() function.
Because the signaling parameter in _Run() is not null, it prevents the function from creating a new signaling instance after the command-line arguments have been evaluated.

Solution

The creation of the signaling and conf objects has been removed from Awake(), and both are now set to null.
By doing this, the signaling object is created inside _Run() using the updated settings that include the values from the command-line arguments.