Apply Capacity Reservation tenancy to AWS instance launch (#3992)

A Capacity Reservation created with non-default tenancy (e.g. `dedicated`)
only accepts instances launched with a matching `Placement.Tenancy`.
Previously dstack always launched with the implicit `default` tenancy, so
runs targeting a dedicated-tenancy reservation failed to match it.

Read `Tenancy` from the reservation dstack already queries in
`create_instance` and pass it through to `create_instances_struct`, which
sets `Placement.Tenancy` when it is non-default. No user-facing config; it
is detected automatically from the reservation and merges cleanly with the
placement-group `Placement` entry.

Assisted-by: Claude

Replace lsblk fs detection with blkid (#3979)

* Replace lsblk fs detection with blkid

* Probe filesystem multiple times

Support targeting specific run instances

Co-authored-by: Federico D'Agostino <fede.dagos@gmail.com>

[JarvisLabs] Support RTX PRO 6000; update gpuhunt dependency (#3943)

* Support JarvisLabs RTX PRO 6000

* Update gpuhunt dependency

* Clean up JarvisLabs SSH keys

* Document JarvisLabs SSH key limit

---------

Co-authored-by: Andrey Cheptsov <andrey.cheptsov@github.com>

[Docs]: Describe image pull progress format

Fix Vast.ai offer order in `dstack offer --fleet` (#3897)

Order by score rather than by price, the same way
offers are already ordered in apply plans and
`dstack offer` without `--fleet`.

Fix unreleased `global_exports` lock on Postgres (#3882)

Kubernetes: add `read_only` volume property (#3838)

If set to `true`, enforces `readOnly: true` in `volumeMounts[]`

Closes: #3837