Decouple Channel Outputs from Interface Binding for Unicast Protocols

[MrPaulAR]

Is your feature request related to a problem? Please describe.
While helping a user today in the zoom room they have a show network and a wifi device on their home network. The FPP show player (v7.5.5) channel output forces a selection of eth0 or wlan0. If he selects eth0 then his Falcons work as expects but no data is sent out wlan0. This is not the first time a user has joined the zoom room with this issue but it is rare.

Confirmed that this setting was the issue because when we changed the "source interface" from wlan0 to eth0 his WLED worked but the Falcons no longer did.

Describe the solution you'd like
Modify the logic of FPP so that if a unicast protocol is selected allow the OS routing to send the data out the proper interface. IE, completely ignore the "source interface" field. However, if the user is still using multicast then honor the source interface.

Describe alternatives you've considered
Told the end user to do one of the following.

• Another FPP on their home network acting as a remote
• Use xSchedule as a remote
• Buy an access point for their show network and move this device to that network
• Specific to this individual recommended moving from WLED to ESPixelStick with SD card

At the end of the day he decided all the given options were too complicated.