Implement Core v1.0.0 Features: Compilation and Patch Review

Problem Overview

patch-hub currently lacks essential features needed for a complete maintainer workflow. Two critical features are missing:

• Ability to compile and test modified kernel trees:
  • Users can apply patches but cannot verify if they compile successfully
• No integration with build systems to test patched code
• No automated validation of patches against common issues
• Limited patch review capabilities:
  • Cannot add comments to patches when replying
  • No dedicated review workflow
  • Cannot easily provide detailed feedback on submitted patches
  • No templates for common review responses

Proposed Features

1. Compiling Modified Trees
   Add the ability to build and test kernel trees after applying patches:

• New "Build" action in the patchset view
• Integration with kw to build the kernel tree specified in config
• Automatic handling of missing .config files, with option to copy from host
• Display of compilation status and errors
• Support for running basic validation tools (e.g., check_patch, coccinelle, kselftest)

2. Reviewing Patches
   Implement comprehensive patch review capabilities:

• New "Review" action in the patch detail view
• Visual line selection similar to Vi/Vim
• Ability to add comments to specific lines or blocks of code
• Email composition with all comments properly formatted
• Templates for common review responses

Start at the patchset view and patch detail view entry points, then inspect the configured kernel-tree workflow and kw integration. Define the build and review boundaries around compilation status, validation-tool results, line comments, formatted email replies, and response templates. Done means both workflows are integrated and expose their requested outcomes to users.