Fix logging with proton

[Etaash-mathamsetty]

Only tested with UMU enabled so far

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[arielj]

"fix" in what sense? what was broken? can you elaborate?

[CommandMC]

Proton's logs don't contain the output of Wine/DXVK/VKD3D-Proton. I was under the impression that this was un-resolveable, but it seems the solution was quite simple after all

IMO this should be a change inside UMU itself. It's going to be enabled in Heroic by default at some point in the future (so logging only working with UMU enabled isn't a problem then), and I expect that Lutris (along with other UMU clients) would require the same / a similar change

[Etaash-mathamsetty]

Superseded by Open-Wine-Components/umu-launcher#279

[Etaash-mathamsetty]

Superseded by Open-Wine-Components/umu-launcher#279

was reverted because it reduced performance (should have been opt-in not opt-out), so reopening this