fix: accept YAML udev discoveryDetails in validating webhook

[twz123]

What this PR does / why we need it:

The udev discoveryDetails are YAML in the Helm templates, sample configurations, and runtime discovery parser, but the validating webhook was parsing them as JSON. That caused valid demo and chart-generated udev configurations to be rejected when the webhook was enabled.

Switch the webhook validation path to YAML parsing and restore the udev e2e fixtures to YAML so validation, tests, and shipped examples all use the same format.

Fixes:

• device mount permission check in webhook #753

Special notes for your reviewer:

If applicable:

• this PR has an associated PR with documentation in akri-docs
• this PR contains unit tests
• added code adheres to standard Rust formatting (cargo fmt)
• code builds properly (cargo build)
• code is free of common mistakes (cargo clippy)
• all Akri tests succeed (cargo test)
• inline documentation builds (cargo doc)
• all commits pass the DCO bot check by being signed off -- see the failing DCO check for instructions on how to retroactively sign commits

[lilustga]

/version patch

[gauravgahlot]

Thank you for your contribution. 💜

You should revert the version.sh file.

[twz123]

You should revert the version.sh file.

That was modified automatically by GitHub Actions in 995bbcf, so I didn't touch that at all. What's the desired way to tackle this? Amend 995bbcf and revert the spurious version edits, or maybe squash the whole automatic commit directly into my commit, fixing this up altogether?

[gauravgahlot]

Thank you @twz123!

Just 2 notes:

1. In the PR description, the 'fixes' points to a PR. If that's not intentional, could you please add the right issue?
2. Are you using Akri at Mirantis or something of your own? Just curious.

[twz123]

Thank you @twz123!

Just 2 notes:

1. In the PR description, the 'fixes' points to a PR. If that's not intentional, could you please add the right issue?

Yes, I intentionally referenced the PR that introduced the regression.

2. Are you using Akri at Mirantis or something of your own? Just curious.

@jnummelin has created a fun talk about Akri and k0s that he and I have been giving at various occasions. My PRs are mainly a result of our debugging attempts when preparing the demos 😅