CI Adjustments

[alexvcodesphere]

Adjusted the ci.yml files to not use the codesphere cli so it can be used as a one click template

[Copilot]

Pull Request Overview

This PR removes the dependency on the Codesphere CLI tool from the CI configuration files to enable the project to be used as a one-click template. The changes eliminate the need for external API tokens and CLI setup, making the deployment process more streamlined.

• Removed Codesphere CLI installation and usage from all CI configuration files
• Replaced CLI-based environment variable setting with direct file creation
• Updated documentation to reflect the simplified setup process

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
ci.yml	Replaced CLI installation and usage with direct environment file creation
ci.QA.yml	Removed CLI dependency and simplified environment variable setup
ci.PROD.yml	Eliminated CLI usage while maintaining environment configuration
ci.DEV.yml	Streamlined setup by removing CLI requirements
README.md	Updated documentation to remove reference to CS_TOKEN requirement
.gitlab-ci.yml	Removed CS_TOKEN environment variable from GitLab CI configuration
.env.sample	Deleted sample environment file that contained CLI-dependent commands

Comments suppressed due to low confidence (1)

ci.PROD.yml:10

• The PATH export is missing in ci.PROD.yml but present in other CI files. This inconsistency could cause the uv command to not be found since it's installed to $HOME/app in ci.yml and ci.DEV.yml but uses nix-env in PROD.

        export UV_PYTHON_BIN_DIR=$PWD/.codesphere-internal/.uv-python-bin

[Simon-Count]

These are actually hard coded environment variables - why not set them directly in each of the integration scripts under, this will set them as Codesphere env vars
ENV: | UV_PYTHON_CACHE_DIR=$PWD/.codesphere-internal/.uv-python etc...