Bug: MOD-UI unnecessary thru audio connections created

[steveb]

Describe the bug
When loading the MOD-UI engine, audio connections are created from system capture_1, capture_2 to mon-monitor in_1, in_2 but mod-ui should be managing all of its own connections.

To Reproduce
Steps to reproduce the behavior:

1. Add Special Chain -> MOD-UI -> MIDI CHANNEL 1
2. View the jack connections in Patchage
3. system capture_1, capture_2 is connected to mod-monitor in_1, in_2

Expected behavior
system capture_1, capture_2 is not connected to mod-monitor in_1, in_2 unless that connection has been explicitly made in the mod-ui pedalboard screen

Screenshots

Setup:

• Software Version: current oram

Additional context
I tried setting audio_thru=False when the engine is "MD" but this had no effect. This bug is a problem for all MOD-UI use because the dry signal is always passed through but there is no visible connection in the mod-ui browser interface. Maybe this needs custom chain setup in the engine start method like for setbfree and aeolus?

Watching Patchage when the engine is started, I can see system capture ports connected to zynmixer input ports, and then mod-monitor is inserted in the middle