Use forks to run instead of cloning ensuring code&action at the same version & Use cache instead of data-persistence branch to run in a public repo at a faster speed

[1208nn]

This pull request refactors and simplifies the GitHub Actions workflow for the Epic Awesome Gamer automation. It removes complex branch management and manual data persistence steps, replacing them with built-in caching and artifact upload mechanisms. The workflow now runs entirely in the main repository context, streamlining setup and execution while improving reliability and maintainability.

Workflow simplification and reliability improvements:

• Removed all steps related to switching branches, cloning external source code, and manually committing/pushing persistence data. The workflow now operates directly in the main repository, reducing complexity and risk of errors. [1] [2] [3]
• Replaced manual persistence and backup steps with GitHub Actions cache and artifact upload for app/volumes/user_data, ensuring automated and reliable data storage between runs. [1] [2] [3]

Dependency and environment setup:

• Updated dependency installation to use uv sync and system package installation in a single step, and standardized Python environment setup to use the main repository’s pyproject.toml.
• Added Playwright browser installation with retry logic, improving robustness of browser-related automation tasks. [1] [2]

Workflow scheduling and execution:

• Changed the scheduled run time to 20:31 UTC and increased the job timeout to 20 minutes for improved reliability. [1] [2]
• Streamlined the main execution step to run the automation directly, with clearer environment variable handling and logging. [1] [2]