[Bug]: CI Workflow fails due to pyink version mismatch between setup.sh and GitHub Actions

## Describe the bug

Currently, there is a version mismatch for `pyink` between the local developer setup and the GitHub Actions workflow ([CPUTests.yml](https://github.com/AI-Hypercomputer/maxdiffusion/blob/main/.github/workflows/CPUTests.yml)).

The `setup.sh` script installs the latest version of `pyink` (currently 25.12.0), while the GitHub workflow strictly enforces `pyink==23.10.0`. As a result, when developers format their code locally using the setup script's version, the CI/CD pipeline fails during the formatting check because it evaluates the code against the older version.

## To Reproduce

Steps to reproduce the behavior:

- Run `bash setup.sh MODE=stable DEVICE=tpu` locally (installs `pyink>=25.12.0`).
- Format the codebase locally using the installed `pyink`.
- Push the changes to a PR.

The GitHub workflow fails on the formatting check because it expects formatting from `pyink==23.10.0`.

## Expected behavior

The version of `pyink` used locally should perfectly match the version enforced by the CI pipeline to prevent unnecessary build failures and contributor friction.