* Add Hot Aisle bare metal support

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Add a flag to release Hot Aisle bare metal without force

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Start Hot Aisle shim with nohup instead of disown

The shim start is now retried until the SSH command succeeds, and
`disown` fails in shells other than bash even though the shim starts.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Connect to Hot Aisle bare metal via ssh_access

The bare metal server's ip_address is private (100.64.0.0/10); SSH is
exposed on ssh_access.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Don't fail Hot Aisle docs commands when nothing is in stock

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Tighten Hot Aisle minimum reservation note

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Silence curl progress in Hot Aisle docs commands

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Recommend fixed fleet nodes for prepaid Hot Aisle instances

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Mark Hot Aisle bare metal as experimental

Keep the no-force flag enabled; drop it once offers carry the minimum
reservation period and instances stay idle until it ends.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

* Make Hot Aisle bare metal opt-in via `bare_metal: true`

Bare metal offers are suggested only if the backend sets `bare_metal: true`,
like RunPod's `community_cloud`. Exclude the field from client requests
when unset to keep older servers working.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

---------

Co-authored-by: Andrey Cheptsov <[email protected]>
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>

- Report `B300 PC` as `B300`.
- Make the `gpu: B300` filter work reliably for
  both `B300 AC` and `B300 PC` variants.

Before:

```shell
$ dstack offer -b vastai --gpu B300

No matching instance offers available. Possible reasons: https://dstack.ai/docs/guides/troubleshooting/#no-offers
```

After:

```shell
$ dstack offer -b vastai --gpu B300

 #  BACKEND                 RESOURCES                                                        INSTANCE TYPE  PRICE
 1  vastai (us-california)  cpu=x86:256 mem=3095.7GB disk=25751.7GB gpu=B300:270GB:8 (spot)  53587615       $73.5377
 2  vastai (us-california)  cpu=x86:256 mem=3095.7GB disk=25751.7GB gpu=B300:270GB:8         53587615       $94.871
 3  vastai (us-california)  cpu=x86:128 mem=773.9GB disk=12875.8GB gpu=B300:270GB:4 (spot)   53587617       $36.7688
 4  vastai (us-california)  cpu=x86:128 mem=773.9GB disk=12875.8GB gpu=B300:270GB:4          53587617       $47.4355
 5  vastai (hr-croatia)     cpu=x86:43 mem=32.2GB disk=810.2GB gpu=B300:270GB:1 (spot)       53579010       $5.411
 6  vastai (hr-croatia)     cpu=x86:43 mem=32.2GB disk=810.2GB gpu=B300:270GB:1              53579010       $10.1485
 7  vastai (hr-croatia)     cpu=x86:86 mem=129GB disk=1620.5GB gpu=B300:270GB:2 (spot)       53579004       $10.822
 8  vastai (hr-croatia)     cpu=x86:86 mem=129GB disk=1620.5GB gpu=B300:270GB:2              53579004       $20.297
```

The fix is in the `gpuhunt` package. This commit
bumps the `gpuhunt` version in `dstack`.

* Update Azure GRID driver to 580.178.04

NVIDIA's 2026-09-30 security bulletin covers A10 vGPU. Azure has patched
the NVadsA10_v5 hosts and now supports only the patched guest drivers:
vGPU 19.6 (580.178.04) and vGPU 20.2.

The 580 driver also adds CUDA 13.0 support on A10. With the previous 570
driver, CUDA 13 images failed with "driver too old" unless they bundled
CUDA forward compatibility libraries, as dstack's base image does. This
matches the 580 driver already used in dstack-cuda images.

Also allow republishing an existing Azure image as a new gallery version,
so dstack servers using dstack-grid-0.14 pick up the new driver without
a release:
- azure_variant input to build only some Azure image variants
- azure_new_gallery_version input to replace the build image and publish
  the next gallery version; without it, publishing stops if a version exists

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Stop Azure image publish if gallery versions can't be listed

Without this, a failed version listing looked like an empty gallery, so
the script tried to publish 0.0.1 again instead of the next version.
Also describe azure_new_gallery_version as a rebuild, since packer
-force deletes and rebuilds the existing managed image.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

---------

Co-authored-by: Andrey Cheptsov <[email protected]>
Co-authored-by: Claude Opus 5.5 <[email protected]>

* Skip placement groups for AWS Capacity Blocks

AWS rejects launches into Capacity Blocks that specify a placement group. Fixes #4344.

* Drop AWS Capacity Block lookup cache and handle missing ReservationType

AWS omits ReservationType for regular capacity reservations.

* Use fleet reservation when provisioning runs

* Bound SSHTunnel control commands with timeouts and BatchMode

* Drop ConnectTimeout from SSHTunnel control commands

* Drop -n from SSHTunnel exec command and document control batch mode

* Use configured Vultr credentials for GPU offers

* Pin temporary gpuhunt dependency to merged commit

* Update gpuhunt to 0.1.33

* Focus Vultr offer test on configured credentials

---------

Co-authored-by: Andrey Cheptsov <[email protected]>

* Reconnect gateway replica SSH tunnels after process exit

* Make SSH cancellation tests compatible with Python 3.10

* Trim SSH tunnel recovery regression tests

---------

Co-authored-by: Andrey Cheptsov <[email protected]>

* Fix gateway recovery after high request load

* Trim gateway authorization regression tests

---------

Co-authored-by: Andrey Cheptsov <[email protected]>