CLI: Interactive file selection for AI suggestions and i18n stats enhancement

[thomas-vilte]

Description

I implemented an interactive file selection mode for the suggest command, allowing users to granularly choose which files are included in the AI-generated commit summary. I also localized the stats command output, including month names and currency formatting, and enhanced the GitHub client with label aliasing and deduplication logic.

Key technical changes include:

• Interactive CLI: Added PromptMultiSelect in the UI package and an --interactive flag to the suggest command.
• Git Service: New GetDiffForFiles method to retrieve diffs for a specific subset of files.
• VCS Enhancements: Implemented labelAliases in the GitHub client to map common labels (e.g., bug to fix) and prevent duplicates.
• Release Logic: Added a safety check to skip binary builds if the main entrypoint is missing, preventing unnecessary failures.
• i18n: Expanded locale files with month names and stats-specific templates.

Fixes #

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

I have updated the test suite to cover the new git service methods and label validation logic.

• Unit tests: Updated git_service_test.go, commit_service_test.go, client_test.go, and stats_test.go.
• Integration tests
• Manual test: Verified the interactive file selection UI and the localized stats output in both English and Spanish.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

🧪 Test Plan & Evidence

Suggested Manual Verification

• API/Backend: Attach JSON response or logs as evidence of correct behavior
• Performance: Ensure no significant latency increase
• Unit Tests: Run go test ./... and ensure all tests pass
• No Regressions: Verify that related features still work as expected