fix(wgsl-in): include user and unknown rules in diagnostic(…) tracking

[ErichDonGubler]

Connections

• Contributes (but does not fully resolve) Support diagnostic filters in WGSL (i.e., diagnostic(…)) #5320.

Description

Prior to this PR, unknown and user diagnostic(…) triggering rules for filters would get ignored, and certain important validations like this were not rejecting the program properly:

fn myfunc() {
	if (true) @diagnostic(off, my.lint) {
		//    ^^^^^^^^^^^^^^^^^^^^^^^^^ not yet supported, should report an error
	}
}

fn myfunc() {
	if (true) @diagnostic(off, wtf) {
		//    ^^^^^^^^^^^^^^^^^^^^^ should emit a warning
	}
}

diagnostic(off, my.lint);
diagnostic(warning, my.lint); // should report a conflict error

diagnostic(off, wat_is_this);
diagnostic(warning, wat_is_this); // should report a conflict error

Testing

• Tests have been added for the above cases, and a bit more. N.B. that operation and validation coverage is missing for standard rule cases still.

Checklist

• Run cargo fmt.
• Run taplo format.
• Run cargo clippy. If applicable, add:
  • --target wasm32-unknown-unknown
  • --target wasm32-unknown-emscripten
• Run cargo xtask test to run tests.
• Add change to CHANGELOG.md. See simple instructions inside file.

[jimblandy]

Looks good to me - thanks!