Executables often fail due to not being launched in the CWD.

### What Happened?

When trying to launch a steam game (just an example) from the executable files seems to do nothing but when ran with the terminal you can see this error:
`/home/allie/.local/share/godot/app_userdata/Luck be a Landlord/install folder/Luck be a Landlord.x86_64: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory`

This is because it's being launched with its full path instead of with the CWD (I think). Opening in Gnome Files works just fine so I imagine they run from the CWD.

### Steps to Reproduce

I obviously can't share the example I'm using here so have this screen recording

https://user-images.githubusercontent.com/13716824/153735767-885d4922-df5f-47d5-84d6-7cd6afd6d98b.mp4

### Expected Behavior

Ideally run executables from the current folder, not their full path or at least show a message when an executable returns non-0 exit code. The former would actually solve the issue and I imagine be easier since there'd be no new UI.

### OS Version

6.x (Odin)

### Software Version

Latest release (I have run all updates)

### Log Output

_No response_

### Hardware Info

_No response_