Add kdeconnect plugin

[safijari]

KDE Connect

When enabled, the plugin manages bringing up kdeconnect and switching over to a different instance of kdeconnect when going between the main UI and a game (because gamescope's use of xwayland is special). With this plugin basic keyboard and mouse input from kdeconnect is now possible in gamemode without any extra effort. Audio can also be adjusted.

Checklist:

Developer Checklist

• I am the original author or an authorized maintainer of this plugin.
• I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.

Plugin Checklist

• I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
• I have verified my plugin is unique or alternatively provides more/alternative functionality to a similar plugin already on the store.

Plugin Backend Checklist

• No: I am using a custom backend other than Python.
• No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
• No: I am using a custom binary that has all of it's dependencies statically linked.

Testing

• Tested on SteamOS Stable/Beta Update Channel.

[TrainDoctor]

@safijari please select a license or if you're sticking with the current license just put your username in there as appropriate. This will be a blocker before it can go to the production store but isn't an issue for going to the testing store. Thanks for your submission!

[TrainDoctor]

Crap, I missed the fact that you don't have a pnpm lockfile. You'll need to re-add that so the plugin will be able to build in CI.

[AAGaming00]

btw assets isn't designed for scripts, it's served by the backend to the frontend to allow for displaying images and such

[safijari]

btw assets isn't designed for scripts, it's served by the backend to the frontend to allow for displaying images and such

What's a better place for it?

Stale

[TrainDoctor]

btw assets isn't designed for scripts, it's served by the backend to the frontend to allow for displaying images and such

What's a better place for it?

Best option imo would be to use the defaults folder as it would put the script in the root directory of the plugin during CI build.

[safijari]

Alright. Did some restructuring and some clean up. This is good to go from my side.

[parkerlreed]

Working great. File transfers and remote control doing what they should.