Refactor pytorch_dev_ubuntu_24.04 Dockerfile to use nightly release

[marbre]

The Dockerfile contains multiple stages (build_rocm, pytorch_sources, pytorch_build, pytorch) which could be at least partly refactored. As a first step build_rocm, which builds ROCm via build_rocm.sh

TheRock/dockerfiles/pytorch-dev/pytorch_dev_ubuntu_24.04.Dockerfile

Line 23 in 463c076

RUN --mount=type=bind,target=/therock/src,rw bash /build_rocm.sh "$AMDGPU_TARGETS"

can be switched over to use the nightly tarball instead of building ROCm "again".

[stellaraccident]

Let's just make sure we keep the path paved so that people can make changes to rocm and produce a pt docker on their own. Folks don't love how slow it is to build this all together but it does enable a development flow that works and we need to not lose that.

[erman-gurses]

Synced with @geomin12 two days ago regarding the artifacts
https://therock-artifacts.s3.us-east-2.amazonaws.com/14366952921/index-gfx110X-dgpu.html
https://github.com/ROCm/TheRock/blob/main/build_tools/fetch_artifacts.py
https://github.com/ROCm/TheRock/blob/main/.github/actions/setup_test_environment/action.yml#L56-L61

[marbre]

Synced with @geomin12 two days ago regarding the artifacts https://therock-artifacts.s3.us-east-2.amazonaws.com/14366952921/index-gfx110X-dgpu.html https://github.com/ROCm/TheRock/blob/main/build_tools/fetch_artifacts.py https://github.com/ROCm/TheRock/blob/main/.github/actions/setup_test_environment/action.yml#L56-L61

These are build artifacts, produced by build_linux_packages.yml whereas the nightly release is produced within portable_linux_package_matrix.yml and the tarball is uploaded to https://github.com/ROCm/TheRock/releases/tag/nightly-release. With build_tools/provision.py there is a script that can help to get either or but as the issue title says I suggest to use the nightly release.

[erman-gurses]

The total duration of building reduced to 34 minutes.

[erman-gurses]

For the remaining items pytorch_sources, pytorch_build, and pytorch, this issue can be opened again in the future however for now build_rocm refactoring is sufficient so issue can be closed after the 388 is landed
cc: @marbre