fixup! tests: dump node-side diagnostics when kata-deploy install fails

The dm-verity rule matched any mention of dmverity, and containerd's own
config dump always contains dmverity_mode, so every failure was reported as
a dm-verity suspect on top of the real one. Match the messages that only
appear when dm-verity actually fails instead.

Signed-off-by: Saul Paredes <saulparedes@microsoft.com>

Author: Redent0r

tests/gha-run-k8s-common.sh

@@ -791,7 +791,8 @@ function kata_deploy_failure_verdict() {
 		matched=1
 	fi
 
-	if sudo grep -qiE 'dmverity|dm-verity' "${journal}" "${configdump}" "${podlog}" 2>/dev/null; then
+	if sudo grep -qiE 'invalid dmverity_mode|dmverity_mode is .on. but|dm-verity support check failed|dm-verity is not supported|EROFS_DMVERITY requires' \
+		"${journal}" "${configdump}" "${podlog}" 2>/dev/null; then
 		echo "SUSPECT 5474f95e04 / 94f673a615 (dm-verity keys written on every path)"
 		echo "  -> dmverity_mode/enable_dmverity are written even with erofsDmverity=false."
 		matched=1