Rocm jaxlib v0.8.0 fixdevtar

[kiran-thumma]

Motivation

Fix packaging.version.InvalidVersion errors during JAX wheel builds caused by ROCm version strings containing multiple + characters (e.g., 7.12.0.dev0+<sha>), which violate PEP 440 version specifier rules.

Technical Details

Modified jax_rocm_plugin/build/rocm/ci_build to sanitize rocm_version by replacing + with . for PEP 440 compliance:

1. Line 60: Sanitize when setting ML_WHEEL_VERSION_SUFFIX for Bazel jaxlib builds
2. Line 178: Sanitize when setting ROCM_VERSION_EXTRA environment variable for plugin/pjrt wheel builds

PEP 440 local version identifiers only allow one + character, and the local segment can only contain alphanumerics and periods. This ensures wheel versions like 0.8.0+rocm7.12.0.dev0.6475192225f38160e614c71cc0543aed2be8fa03 are valid.

Test Plan

• Build JAX wheels with dev rocm_version containing + (e.g., 7.12.0.dev0+6475192225f38160e614c71cc0543aed2be8fa03)
• Verify jaxlib, jax-rocm7-plugin, and jax-rocm7-pjrt wheels build successfully
• Verify wheel filenames contain sanitized version strings

Test Result

• All three wheels build without InvalidVersion errors
• Wheel filenames correctly use . instead of second + in version string
• https://github.com/ROCm/TheRock/actions/runs/21718314934

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

[kiran-thumma]

Tested : https://github.com/ROCm/TheRock/actions/runs/21729822178