KVM: Add fuzz tests for new KVM Redfish APIs

[amarnath-ac]

Create fuzz coverage for newly introduced KVM Redfish APIs to improve robustness against malformed or unexpected input and prevent regressions in request parsing, validation, and error handling.

Scope:

1. Add fuzz tests for new KVM endpoints (request consent, submit consent code, cancel consent, and related new actions).
2. Fuzz path params, JSON payloads, content types, and edge-case/invalid values.
3. Verify handlers return stable and expected HTTP status codes for invalid and random inputs.
4. Ensure no panics, crashes, or hangs under fuzz execution.
5. Integrate fuzz targets with existing redfish handler test structure and CI-compatible commands/documentation.

Acceptance criteria:

1. Fuzz tests exist for all newly added KVM APIs.
2. Running fuzz targets for a defined duration completes without panic/crash/hang.
3. Invalid/malformed inputs consistently return controlled error responses (no 500 from parser/runtime failures unless expected by contract).
4. go test for affected packages passes with fuzz targets included.
5. CI/lint/build remain green after fuzz test addition.