Smart module version resolution during terraform init.

[alex-kattathra-johnson]

Smart Module Version Resolution During Terraform Init

This PR implements smart module version resolution during terraform init to automatically resolve version conflicts and optimize module dependency selection using a
PubGrub-inspired constraint solving algorithm.

Changes Proposed

• Smart Constraint Solving: Implements a global constraint solver that considers all module dependencies simultaneously to find optimal version selections
• Lazy Module Resolution: Uses lazy loading and caching for efficient resolution of module versions and metadata
• Provider Analysis: Analyzes provider requirements from module sources to ensure compatibility
• Graceful Error Handling: Converts resolution failures to warnings to avoid blocking installation while providing useful feedback
• Performance Optimization: Caches resolved versions and module metadata to minimize repeated network calls

Technical Implementation

• ModuleConstraintSolver: Core solver implementing PubGrub-inspired algorithm for dependency resolution
• LazyModuleResolver: Efficient lazy loading of module versions with caching and conflict detection
• ModuleProviderAnalyzer: Extracts and analyzes provider requirements from module sources
• Integration: Seamlessly integrates with existing ModuleInstaller workflow during terraform init

Rationale

Currently, Terraform installs modules sequentially without global constraint solving, which can lead to suboptimal version selections and unnecessary conflicts. This
enhancement provides:

1. Better User Experience: Automatically resolves version conflicts without manual intervention
2. Optimal Version Selection: Prefers newer versions while respecting all constraints
3. Performance: Reduces installation time through intelligent caching and lazy loading
4. Backward Compatibility: Maintains existing behavior when no conflicts exist

Testing

• Comprehensive unit tests for all new components
• Integration tests with real registry modules (TF_ACC tests)
• Performance testing with complex dependency scenarios
• Regression tests to ensure backward compatibility

Fixes #37405

Target Release

1.14.x

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

No changes to security controls. This enhancement operates within existing security boundaries and does not modify access controls, encryption, or logging mechanisms.

CHANGELOG entry

• This change is user-facing and I added a changelog entry.
• This change is not user-facing.

Added changelog entry: .changes/v1.14/ENHANCEMENTS-20250805-120000.yaml

[crw]

Per the previous PR comment: https://github.com/hashicorp/terraform/blob/main/.github/CONTRIBUTING.md#proposing-a-change

This is unlikely to be reviewed for the above reason. Also, looks like it was generated via LLM? Now that the IBM acquisition has been completed, we will need to review what can be considered an acceptable contribution when it comes to modern code assist tooling. Thanks!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.