Add findings-to-fixes documentation

[milansamuel609]

Hi @dsoumis,

This PR adds the Findings-to-Fixes documentation for jws-diag.

Summary

The guide includes:

• An overview of the validation workflow and severity levels.
• Instructions for running validation in both the default human-readable format and JSON format.
• Example validation outputs for both human-readable and JSON formats.
• A complete mapping of all implemented validation rules to their:
  • Category
  • Severity
  • Description
  • Source file
  • Recommended resolution
• Guidance for verifying that reported findings have been resolved.
• Documentation describing how validation results are included in the generated support bundle (validation-results.json).
• Additional notes covering runtime-dependent findings and the read-only behavior of the validation engine.

Verification

• Verified that the document renders correctly on GitHub (headings, tables, and code blocks).
• Verified that all command examples and example outputs are consistent with the current implementation.

Clarification

I have a couple of questions regarding the documentation:

• Since the jws-diag bundle command is now implemented, would you prefer a dedicated guide for it (similar to the Findings-to-Fixes Guide), or is the current level of documentation sufficient?

• Would you also recommend adding references to the documentation in the project's README.md, or would you prefer to keep the README.md minimal?

[milansamuel609]

Hi @dsoumis,

Along with the exit codes table, I also made a few additional documentation improvements around the validation output.

• Added explanations for the human-readable and JSON output formats, including what the findings, summary, and exitCode fields represent.
• Also documented the severity levels and their meanings.