[Bug]: The dotnet481 dependency being installed causes install .exe's for software requiring dotnet to attempt installing to whatever directory the .exe is in, instead of the bottle or the appropriate folders within it.

[BugsyReportsy]

Describe the bug

When I tried to install osu! when dotnet481 was installed on my bottle, the logs indicated the installer failed because it was trying to install the game to my Z Downloads folder. When I tried again after dragging osu!install.exe into my bottle's internal Downloads folder, it dumped out the game files there. Only after I uninstalled dotnet481 and installed dotnet48, I was able to install the game properly.

To Reproduce

1. Create a gaming bottle that uses Wine GE 8-26, Proton GE 9-23, or Kron4ek wine 10.0 as a runner.
2. Install dotnet481 in Dependencies.
3. Run osu!install.exe from the system Downloads folder with Run in Terminal on.
4. Copy osu!install.exe into the bottle's internal Downloads folder, then run it with Run in Terminal on.

Package

Flatpak from Flathub

Distribution

Linux Mint 22.1

Debugging Information

Official Package: true
Version: '51.18'
DE/WM: cinnamon
Display:
    X.org: true
    X.org (port): :0
    Wayland: false
Graphics:
    vendors:
        nvidia:
            vendor: nvidia
            envs:
                __NV_PRIME_RENDER_OFFLOAD: '1'
                __GLX_VENDOR_LIBRARY_NAME: nvidia
                __VK_LAYER_NV_optimus: NVIDIA_only
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/nvidia_icd.json
            nvngx_path: /usr/lib/x86_64-linux-gnu/GL/nvidia-550-120/extra/nvidia/wine
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.8.0-52-generic
Disk:
    Total: 33591869440
    Free: 33591681024
RAM:
    MemTotal: 62.6GiB
    MemAvailable: 58.0GiB
Bottles_envs: null

Troubleshooting Logs

Additional context

Bottles is running with permission to access all user files, which was granted via Flatseal.

This bug is similar to one I had last year, where if Proton GE was selected as my runner, it would always attempt to install to where ever the install .exe was. This bug seems to have been fixed now, though I was on Pop!_OS 22.04 back then.