EP: Implement compile validation and e2e

[zhenchaoni]

Our supported device for each ep is:

• qnn: npu and gpu
• openvino: npu, gpu and cpu
• vitisai: npu
• nv_tensorrt_rtx: gpu

This PR

1. Add "good input" e2e test cases, it permutates the above support matrix to generate --device and --ep combinations for e2e test.
2. Add a validation logic. If the user provides --device and --ep which doesn't match the above matrix, or the user provides ep that is not applicable to his machine, a validation error will be raised.

[DingmaomaoBJTU]

Code review

Found 1 issue:

1. _BAD_INPUT_PARAMS row 3 uses the wrong EP guard — require_ep("openvino") only guarantees OpenVINO is present on the host, but the test asserts that QNN is absent (expected error: "is not available on this host"). On a machine with both OpenVINO and QNN installed, the test will run (OpenVINO guard passes), the compile with --ep qnn will succeed (QNN is available), and the assertion exit_code != 0 will fail.

winml-cli/tests/e2e/test_compile_e2e.py

Lines 706 to 711 in ed31917

	# 3. EP not registered on this host.
	(None, "qnn", "openvino", "is not available on this host"),
	# 4. No available EP on this host supports the requested device.
	("cpu", None, "qnn", "does not support EPContext compilation"),
	]

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}