fix: Update Terraform MCP server tool permissions

[lgallard]

Fix Tool Permissions for HashiCorp Terraform MCP Server

Problem Identified

After fixing MCP connectivity, workflow failing due to tool permission mismatch:

• MCP Connectivity: Both terraform and context7 servers connecting successfully
• Tool Permissions: Claude trying to use mcp__terraform__get_latest_provider_version but only mcp__terraform-server__* tools were allowed

Root Cause

HashiCorp Terraform MCP server uses different tool naming pattern than expected:

• HashiCorp Server Tools: mcp__terraform__search_providers, mcp__terraform__get_provider_details, etc.
• Previous Workflow: Expected mcp__terraform-server__getProviderDocs, mcp__terraform-server__resolveProviderDocID, etc.

Solution

Updated allowed_tools to match HashiCorp MCP server actual tool names for providers, modules, and policies toolsets.

Evidence

MCP servers now show connected status but tool permission errors prevent execution.

Resolves: #224

[lgallard]

🎉 SUCCESS! This PR fixes Issue #224

✅ Validation Results

Latest Workflow Run: https://github.com/lgallard/terraform-aws-backup/actions/runs/17365092199

MCP Server Connectivity - RESOLVED ✅

• Terraform: "status": "connected"
• Context7: "status": "connected"
• Evidence: Both servers connecting successfully via Docker and NPX respectively

Tool Permissions - RESOLVED ✅

• Before: Permission errors for HashiCorp tool names
• After: All tools accessible, no permission errors
• Fix: Updated allowed_tools to match HashiCorp server's actual API

Claude Code Feature Discovery - WORKING ✅

• Status: "conclusion": "success"
• Duration: 4+ minutes of successful execution
• Evidence: Full analysis completed, feature discovery functional

Issue Creation

• No new features discovered (module appears up to date)
• Workflow properly configured for issue creation when features found

📋 Technical Resolution Summary

1. MCP Connectivity: Fixed by switching to official HashiCorp Docker-based terraform-mcp-server
2. Tool Permissions: Fixed by updating allowed_tools to match HashiCorp server's naming convention
3. End-to-End Functionality: Verified working via successful 4+ minute workflow execution

Ready to merge - Issue #224 is resolved! 🚀