Weird situation when DotNetDriver is running and then open any scenario the WindowsDriver or UnixDriver runs

[BDisp]

Describe the bug

On Windows:

• When DotNetDriver is running, opening any scenario cause the WindowsDriver to run.

On Linux and macOS:

• When DotNetDriver is running, opening any scenario cause the UnixDriver to run.

To Reproduce

Steps to reproduce the behavior:

• Run DotNetDriver
• Put a breakpoint in the NetInput Peek method
• The breakpoint is hit, so DotNetDriver is running
• Open any scenario
• Put a breakpoint in the NetInput Peek method
• The breakpoint is not hit, so DotNetDriver is not running
• Put a breakpoint in the WindowsInput or UnixInput Peek method
• The breakpoint is hit, so WindowsDriver or UnixInput is running

2. Expected behavior: (describe what should happen)

When opening a scenario the current DotNetDriver instance is disposed and a new DotNetDriver is initialized.

3. Actual behavior: (describe what actually happens)

On Windows:

• When opening a scenario the current DotNetDriver instance is disposed and a new WindowsDriver is initialized.

On Linux and macOS:

• When opening a scenario the current DotNetDriver instance is disposed and a new UnixDriver is initialized.

[tig]

ForceDriver used to be a static. It's now an instance property in IApplication.

I likely failed to update UI catalogs logic for starting a scenario to account for this.

[tig]

Probably the right way to fix this is by having uicatalogs command line support set ForceDrfault in CM.RuntimeConfig instead of setting Application.ForceDriver directly.