Make CI release type explicit and limit workflow_dispatch inputs to [ci, dev]

[ScottTodd]

Motivation

Follow-up to:

• Plumb release_type through multi_arch workflows #4408
• Split multi-arch pytorch release workflows for future configure/build/test jobs #5452 (comment)

This changes the release type used throughout workflows and associated scripts for CI runs (starting from multi_arch_ci.yml or equivalent) from using "" (empty string) to using "ci".

With that in place, it then replaces all uses of the release_type input for workflow_dispatch events with a choice input type that only allows [dev] or [ci, dev], preventing developers from triggering nightly or prerelease builds from this repository. All releases with those types should be triggered in https://github.com/ROCm/rockrel instead (where permissions will be more limited).

Test Plan

• I spot checked a few workflows in the UI
  • multi_arch_build_tarballs.yml --> https://github.com/ROCm/TheRock/actions/runs/26544216544 --> https://therock-ci-artifacts.s3.amazonaws.com/26544216544-linux/tarballs/index.html
  • release_portable_linux_packages.yml
    
• Watch CI and nightly release results for any unexpected changes to bucket selection

Submission Checklist

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

Generated with Codex

[ScottTodd]

Several of the Windows test failures are #5163 (corrupt uv package cache is causing uv pip install requests to fail)