treewide: remove jovian-steam-protocol-handler, just call normal Steam

[K900]

Our bootstrap script can handle this now.

[K900]

So this fails because every one of our attempts of calling Steam calls it with -steamdeck, which breaks the rest of the argument passing, because idk. Presumably this is also why this was done this way upstream. I guess we keep the hack for now.

[samueldr]

(from a discussion in the matrix room)

TLDR: argument parsing / "steam protocol handling" is uh... not uniified in the codebase, and some parts are handled with idiosyncrasies.

For example, the power button press handling:

~ $ echo 'steamed-hams -ifrunning -steamdeck steam://longpowerpress' > .steam/steam.pipe 
# fails

~ $ echo 'steamed-hams -ifrunning steam://longpowerpress -steamdeck' > .steam/steam.pipe                                             
#fails

~ $ echo 'steamed-hams -ifrunning steam://longpowerpress' > .steam/steam.pipe 
#works

• argv[0] can be anything (no need for the string steam to exist)
• argv[1] must be -ifrunning
• argv[2] the power button press

This is not limited to the pipe, see:

~ $ steam-run .local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-steam-remote -ifrunning steam://longpowerpress -steamdeck
# fails

~ $ steam-run .local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-steam-remote -ifrunning steam://longpowerpress
# works

So the argv0 semantics follow a "command line call" semantic too.