refactor: show table headers in console and handle exits

[Demolus13]

Summary

This PR restructures the console rendering code to show table headers of verify-policy command, centralize table creation, add per-dependency rendering, move check-summary updates to the analyzer, clean up progress handling, and ensure the console output is checked for any Processing and marked as Failed before stopping or exiting.

Description of changes

• Column names updated to Component ID, PURL, Policy Name for verify-policy command.
• Introduced TableBuilder to centralize table construction and avoid repetitive table-building code. Many smaller helper methods were added (e.g. _make_checks_table, _make_failed_checks_table, _make_summary_table, mark_failed).
• Added a Dependency class to represent and render per-dependency analysis sections (description, progress, failed checks, and summary) and allow rendering for dependency lists.
• RichConsoleHandler was refactored to compose the live layout from reusable tables and dependency make_layout().
• Calls that previously updated the console from the report/result objects were moved into the analyzer flow. The update_checks_summary() calls now happen from src/macaron/slsa_analyzer/analyzer.py for both the main record and dependency records so the console UI receives updates as analysis completes.
• remove_progress_bar() is called when checks complete to ensure the progress task is removed from the live progress bar.
• The mark_failed() method was added/extended to convert any in-progress Status entries to a failed state and is invoked when stopping or exiting.
• Added a new "Logging and Console Output" section to docs/source/pages/developers_guide/style_guide.rst that documents the macaron.console use and how to interact with the rich handler.

Related issues

N/A

Checklist

• I have reviewed the contribution guide.
• My PR title and commits follow the Conventional Commits convention.
• My commits include the "Signed-off-by" line.
• I have signed my commits following the instructions provided by GitHub. Note that we run GitHub's commit verification tool to check the commit signatures. A green verified label should appear next to all of your commits on GitHub.
• I have updated the relevant documentation, if applicable.
• I have tested my changes and verified they work as expected.