Add SDV 1-VM and 2-VM presubmit E2E tests

[SuperStrongDinosaur]

This PR introduces end-to-end presubmit test coverage for SDV targets under e2etests/cvd/sdv_tests.

The test suite validates SDV device lifecycle operations (status querying, graceful stop, start, and restart) and multi-VM isolation based on the device-host interaction baseline tests:
- Single-VM lifecycle operations (sdv_fw_baseline_dhi_1vm_test.py)
- Two-VM multi-instance lifecycle and isolation (sdv_fw_baseline_dhi_2vm_test.py)

BUG: b/559633154

[chihchiachen]

Instead of treating SDV CF as an outlier, a better approach is to generalize the new test cases so they can optionally support non-SDV CF variants.

So I recommend the following changes:

• Generalize sdv_1vm_test as lifecycle_test and use it to replace cvd_create_tests.
• Generalize sdv_2vm_test as isolation_test, apply it to sdv_media + sdv_core, and then clean up the dupplicate config from cvd_load_tests.

@Databean please let me know your thoughts.

[Databean]

a better approach is to generalize the new test cases so they can optionally support non-SDV CF variants.

Most of the tests do look pretty general, except for the GetSyspropStringForDevice parts.

[SuperStrongDinosaur]

Instead of treating SDV CF as an outlier, a better approach is to generalize the new test cases so they can optionally support non-SDV CF variants.

So I recommend the following changes:

• Generalize sdv_1vm_test as lifecycle_test and use it to replace cvd_create_tests.
• Generalize sdv_2vm_test as isolation_test, apply it to sdv_media + sdv_core, and then clean up the dupplicate config from cvd_load_tests.

@Databean please let me know your thoughts.

Thanks for the feedback @chihchiachen. Generalizing the lifecycle and multi-instance isolation tests across other CF targets is definitely a right long-term direction. In this PR, my goal is to have the foundational presubmit coverage required specifically for SDV targets without affecting existing CI pipelines

Now that the CVD lifecycle methods are decoupled into free functions under e2etests/cvd/common/cvd.go, we can build a generalized lifecycle_test and isolation_test in a dedicated follow-up PR once we define common identity checks for standard CF