Update DiscordStatus to v1.6.0

[andrewburgess]

Update DiscordStatus to v1.6.0

• Adds ability to set a custom device name within the rich presence activity reported to Discord
• Adds option to override the fallback application ID (hidden behind "Advanced Settings", uses the default one I created when I started this plugin, but have since adjusted from using "Steam Deck" as the application name to a more generic "Steam" name since there are more devices available now)
• Various attempts to try to resolve stale activity reporting (interval checks to ping Discord RPC socket with activity status versus the previous attempt to tie in to Steam's lifecycle notifications, reworking how the socket "Pipe" is handled to hopefully be more consistent over long term usage)
• Improved matching against Discord's "detectable" application list, using the Steam appId if available, and then falling back to exact name matching, or normalized name matching as the last resort.

Separately, for plugin development purposes, reworked the build/deployment process to drop the dependency on Docker and WSL that I previously needed

Task Checklist

Developer

• 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.
• Generative AI was NOT used to write a majority of the code I am submitting.
  • For this update, I did use generative AI to assist in reworking my deployment process, as well as helping me solve some of the RPC/lifecycle issues that have been raised over time. I'm not sure what the thresholds are for this checkbox item, but the majority of the code for this plugin is written by me, but for this update in particular, there was AI usage.

Plugin

• 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 provides more/alternative functionality to a plugin already on the store.

Backend

• 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.

Community

• I have tested and left feedback on two other pull requests for new or updating plugins.
• I have commented links to my testing report in this PR.

Testing

• Tested by a third party on SteamOS Stable or Beta update channel.

[github-actions]

Issues Found

No issues with your PR description were found.

Next Steps

1. If we found any issues above, please edit your pull request description to resolve them and leave a comment saying you've done so.
2. For the quickest review, please see the Community section of the pull request template for how you can help other developers.
3. Once your description is correct, a maintainer will review your pull request as soon as possible.

Thank you for your contribution! If you need any help, please reach out on our Discord server. ❤️

[github-actions]

This pull request is stale as no updates or testing reports have been posted within the last 7 days. Please ensure you are actively recruiting testers or resolving the issues discussed. If you do not remove the stale label or comment, this will be closed in 7 days. Please close this pull request if you need more time to resolve issues so we can keep our repo healthy.

[andrewburgess]

Not stale, not sure if build action can be retriggered though so that it can make it to the testing store?