feat: Add automated Route53 Resolver Rules feature discovery

[lgallard]

Summary

This PR introduces automated weekly feature discovery for the terraform-aws-route53-resolver-rules module using Claude Code with enhanced MCP server integration.

What's Added

• GitHub Actions Workflow (.github/workflows/feature-discovery.yml)
  • Weekly automated scans every Sunday at 00:00 UTC
  • Manual trigger support with configurable options
  • Dry-run mode for testing
• Feature Tracking Database (.github/feature-tracker/route53-resolver-features.json)
  • Tracks current implementation state for Route53 Resolver resources
  • Maintains discovery history and statistics
  • Pre-configured with existing module capabilities

How It Works

1. MCP Server Integration: Uses Terraform and Context7 MCP servers for up-to-date documentation
2. Intelligent Analysis: Compares AWS provider Route53 Resolver resources with current module implementation
3. Automated Issue Creation: Creates structured GitHub issues for new features, deprecations, and important bug fixes
4. Progress Tracking: Maintains comprehensive database of discoveries and actions taken

Key Features

• Route53 Resolver-Specific Focus: Analyzes AWS Route53 Resolver rules, associations, and query logging features
• Smart Filtering: Avoids false positives and duplicate issue creation
• Manual Controls: Supports manual execution with provider version specification
• Current State Tracking: Pre-populated with existing module resources and capabilities

Manual Execution

# Standard weekly discovery
gh workflow run feature-discovery.yml

# Dry run mode (no issues created)
gh workflow run feature-discovery.yml -f dry_run=true

# Specific provider version
gh workflow run feature-discovery.yml -f provider_version=5.82.0

Current Implementation Tracked

• aws_route53_resolver_rule - DNS forwarding rules creation and management
• aws_route53_resolver_rule_association - VPC associations for DNS forwarding
• Data sources for rule discovery and query capabilities
• Support for both basic and complete implementation patterns

DNS-Specific Features Supported

• Conditional Forwarding: Domain-specific DNS forwarding to target servers
• Multi-VPC Support: Association of rules across multiple VPCs
• Cross-Account Sharing: RAM sharing for centralized DNS management
• IP Address Flexibility: Support for both implicit and explicit port specifications
• FQDN Validation: Proper handling of fully qualified domain names
• High Availability: Multiple target IP support for DNS failover

Integration

• Compatible with existing release-please workflow
• Uses conventional commit format for automatic changelog generation
• No impact on current development workflow
• Designed for immediate deployment without breaking changes

This automation ensures the module stays current with AWS Route53 Resolver service evolution while maintaining high DNS resolution performance and comprehensive documentation.