[ROCm][Bugfix] Revert removing setuptools version restriction

[gshtras]

Reverting #28337 on ROCm specific files until a proper solution is found. Other platforms might suffer from a similar issue

The underlying issue mentioned in #17320 is still not fixed properly.
To elaborate, setuptools>=80 will replace python setup.py develop with pip install -e ., which creates an isolateb build environment and pulls build dependencies from pyprojec.toml. In particulat it would try to install torch==2.9.0, which is a CUDA version of torch package by default, so the ROCm build would fail.
The only possible way to build currently is with bdist_wheel, which doesn't allow creating a development environment

[gemini-code-assist]

Code Review

This pull request correctly reverts the setuptools version restriction to <80.0.0 for ROCm-specific files to fix a build issue. My review points out that this fix should be applied more broadly to other requirement files and the pyproject.toml to ensure consistency and prevent similar build failures on other platforms, as hinted in the pull request description.

[gemini-code-assist]

While this change correctly pins setuptools to <80.0.0 for ROCm builds, several other files still allow versions up to <81.0.0. As noted in the PR description, this could lead to the same build issues on other platforms. For consistency and to prevent potential failures, it's recommended to apply this version restriction more broadly.

The following files also contain setuptools<81.0.0 and should likely be updated to <80.0.0:

• pyproject.toml (line 7)
• requirements/build.txt (line 5)
• requirements/common.txt (line 38)
• requirements/cpu-build.txt (line 4)
• requirements/xpu.txt (line 8)

[tjtanaa]

LGTM