Transfer LetMeReShade to Cliffback and update to v1.8.1

[Cliffback]

Transfer LetMeReShade from itsOwen to Cliffback

This PR transfers the LetMeReShade plugin to the actively maintained fork (Cliffback/LetMeReShade) and updates the store listing to the latest stable release, v1.8.1.

The original repository (itsOwen/LetMeReShade) is no longer actively maintained. Its README explicitly directs users to Cliffback/LetMeReShade as the current, maintained version for continued development and support. This transfer ensures the Decky plugin store continues to serve the actively maintained release.

The goal is to keep the plugin updated with new ReShade releases, streamlining the codebase (the single large python file is unwieldy), and address open issues.

Regarding the 1.8.1 release, most of the changes are code quality related. I introduced a few linters for the different languages involved, so most of the files have been updated to comply with the rules. The user facing changes are minimal, and related to bug fixes.

itsOwen@1.8.0 → Cliffback@v1.8.1

The release PR for 1.8.1 contains the changelog: https://github.com/Cliffback/LetMeReShade/releases/tag/v1.8.1

Reasons for Changing Ownership

The original author, itsOwen, has endorsed the transfer and updated their README to point users to Cliffback/LetMeReShade as the maintained fork.

This fork contains the latest release (v1.8.1), bug fixes, and CI improvements not present in the original repository. The original repository is effectively archived; the Cliffback fork is the only source of active development and support.

Task Checklist

Developer

• The original author or authorized maintainer of this plugin has either agreed to the transfer or has been unresponsive for an extended period as described above.
• I am accept the responsibility of becoming the 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.*

"The original plugin predates the AI disclosure policy. I cannot speak for the original codebase, but under my maintenance, AI has been used for tooling and infrastructure (CI, test build scripts, etc), while the plugin functionality itself (backend, frontend) remains largely unchanged with just a few bug fixes."

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.

*Been tested on non-offical hardware running Steam Gamescope

Backend

• No: I am using a custom backend other than Python.
• Yes: 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.

"The plugin uses ReShade"

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

• Both testing boxes are present in your description. Please remove one of them per the Markdown comment above the testing section.

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. ❤️

[Cliffback]

Have updated the description now