fix(simulator): identify simulated Nitro Enclave guests

[kvinwang]

Problem

Simulated Nitro Enclave guests were not identified as Nitro in guest-side platform detection. Code selecting attestation and measurement behavior therefore took the generic/non-Nitro path even though the guest used the Nitro simulator.

Root cause and fix

Recognize the DMI identity installed by the guest-side simulator and skip the TDX-only MR_CONFIG_ID check for Nitro Enclave guests.

The simulator remains the single owner of simulated DMI identity. The VMM does not override QEMU SMBIOS.

Implementation

• fix(simulator): detect Nitro Enclave DMI
• fix(guest): skip TDX config check on Nitro Enclave

Changed paths:

• dstack/dstack-types/src/lib.rs
• dstack/dstack-util/src/system_setup/config_id_verifier.rs

Scope

This PR addresses one logical simulator finding. It intentionally excludes the acceptance-test infrastructure from #841 and unrelated product fixes from #840.

Dependency and merge order

This PR is based directly on master and does not require another split product PR to merge first.

Verification

• cargo test -p dstack-types detects_nitro_enclave_from_simulated_dmi: passed
• cargo test -p dstack-util nitro_enclave_does_not_require_tdx_mr_config: passed
• git diff --check origin/master...HEAD: passed

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.