fix: implement GitHub issue creation for AWS Backup feature discovery

[lgallard]

Summary

Fixes the AWS Backup Feature Discovery workflow to actually create GitHub issues when new features are discovered.

Problem

The workflow was successfully discovering AWS Backup features (found 7 new features) but not creating GitHub issues for them. Features were marked as "status": "pending_creation" instead of being tracked as actual issues.

Solution

1. Enhanced Claude Code Prompt: Added explicit instructions for issue creation with detailed templates
2. Post-Processing Step: Added backup mechanism to create issues for any features marked as "pending_creation"
3. Workflow Summary: Enhanced reporting to show issue creation status
4. Issue Templates: Standardized issue format with auto-discovery metadata

Changes Made

• Updated Claude Code direct_prompt with explicit GitHub issue creation commands
• Added Post-process pending issue creation step after Claude Code execution
• Enhanced workflow summary to track issue creation statistics
• Improved error handling and validation

Testing

• Modified workflow tested with force_scan=true and dry_run=false
• Claude Code step completed successfully
• Workflow properly handles both dry-run and production modes

Expected Results

• 5 GitHub issues will be created for the discovered AWS Backup features:
  • aws_backup_global_settings
  • aws_backup_logically_air_gapped_vault
  • aws_backup_region_settings
  • aws_backup_restore_testing_plan
  • aws_backup_restore_testing_selection

Fixes

• Resolves issue where features were discovered but no tracking issues created
• Ensures reliable issue creation for future feature discoveries
• Provides proper audit trail of discovered features