[Validation] Add validation and tests for invalid system values in incompatible node launch type

[bob80905]

#5827 first requires validation at the DXIL level. The validation will check for functions that have incompatible node launch types, and intrinsics that represent certain system values.
This PR implements this validation and adds some tests that exercise this validation.
Fixes #6104

[github-actions]

⚠️ Python code formatter, darker found issues in your code. ⚠️

You can test this locally with the following command:

darker --check --diff -r 3ef6ca2f94658de919732bae1aa03d69c003bb4b..4dcddfb10f29cb6bb5b8dd8a22a57ffda3abff2a utils/hct/hctdb.py

View the diff from darker here.

--- hctdb.py	2023-12-15 00:36:28.000000 +0000
+++ hctdb.py	2024-01-24 19:25:16.774761 +0000
@@ -7553,11 +7553,11 @@
             "Instr.AtomicIntrinNonUAV", "Non-UAV destination to atomic intrinsic."
         )
         self.add_valrule_msg(
             "Instr.SVConflictingLaunchMode",
             "Input system values are compatible with node shader launch mode.",
-            "Call to DXIL intrinsic %0 (%1) is not allowed in node shader launch type %2"
+            "Call to DXIL intrinsic %0 (%1) is not allowed in node shader launch type %2",
         )
         self.add_valrule("Instr.AtomicConst", "Constant destination to atomic.")
 
         # Work-Graphs
         self.add_valrule(

• Check this box to apply formatting changes to this branch.

[tex3d]

LGTM.