chore: upgrade microsoft/fabric provider to 1.10.0

[PratikWayase]

Description

Upgrades the microsoft/fabric Terraform provider from 1.3.0 to 1.10.0 across all Fabric-related Terraform components and blueprints. This PR also enables skip_capacity_state_validation = true for the Fabric workspace resource to avoid validation failures when non-production Fabric capacities are paused or suspended.

Related Issue

Fixes #494

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)
• Blueprint modification or addition
• Component modification or addition
• Documentation update
• CI/CD pipeline change
• Other (Terraform provider version upgrade)

Implementation Details

• Updated all Fabric Terraform provider version constraints to 1.10.0.
• Replaced the >= 1.3.0 constraint with a pinned 1.10.0 version.
• Added skip_capacity_state_validation = true to the Fabric workspace resource as recommended in the issue description.

Testing Performed

• Terraform plan/apply
• Blueprint deployment test
• Unit tests
• Integration tests
• Bug fix includes regression test
• Manual validation
• Other: Changes are limited to Terraform provider version constraints. Azure-dependent validation (terraform validate/npm run tf-validate) could not be executed locally because an Azure subscription is required. CI will perform validation.

Validation Steps

1. Verify all Fabric Terraform modules reference provider version 1.10.0.
2. Run npm run tf-validate.
3. Run npm run tflint-fix-all.
4. Confirm Terraform initializes successfully with the updated provider.

Checklist

• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have run terraform fmt on all Terraform code
• I have run terraform validate on all Terraform code
• I have run az bicep format on all Bicep code
• I have run az bicep build to validate all Bicep code
• I have checked for any sensitive data/tokens that should not be committed
• Lint checks pass (run applicable linters for changed file types)

Security Review

• No credentials, secrets, or tokens are hardcoded or logged
• RBAC and identity changes follow least-privilege principles
• No new network exposure or public endpoints introduced without justification
• Dependency additions or updates have been reviewed for known vulnerabilities
• Container image changes use pinned digests or SHA references

[rezatnoMsirhC]

skip_capacity_state_validation = true is hardcoded here without an input variable, which means every deployment (including production) skips Fabric capacity state validation. The codebase convention for internal modules requires all variables to be required with no defaults.

Consider adding a required variable to the module:

variable "skip_capacity_state_validation" {
  type        = bool
  description = "When true, skips validation of Fabric capacity state during workspace provisioning. Useful for non-production environments where capacity may be paused."
}

Then thread it through src/000-cloud/031-fabric/terraform/main.tf when calling module.fabric_workspace, and set it to true in the CI deployment config (src/000-cloud/031-fabric/ci/terraform/). This lets production callers opt out of skipping validation, giving them a faster failure signal when deploying against a paused or misconfigured capacity.

[katriendg]

Thank you for taking on this one, it's pretty complete just missing a few elements to function and pass build.

Add the variable default setting - see inline comment.
Rebase onto latest main. main has moved since this branch was cut — notably #627 added generated ci/terraform/README.md files (including for this component), so rebasing first avoids a docs conflict.
Regenerate Terraform docs after the rebase by running npm run tf-docs. The new variable isn't reflected in the component or CI README.md yet, and generated docs must not be hand-edited. Also the docs will regenerate because of provider version update.

Once those three are in and terraform validate passes on both blueprints, this should be good to go. Thanks again for helping keep the Fabric provider current!

[katriendg]

At the component root level this variable needs a default. Per the repo guideline, a component's public interface variables are optional with a sensible default, while internal module variables (e.g. modules/workspace/variables.tf) stay required with no default — that part is already correct here.

As written (no default), skip_capacity_state_validation becomes a required argument, which breaks every consumer that doesn't pass it. I validated locally and both fabric and fabric-rti blueprints fail terraform validate with Missing required argument. Your ci/terraform/variables.tf variant already sets default = true, so this looks like an accidental omission.

Suggested

variable "skip_capacity_state_validation" {
  type        = bool
  description = "When true, skips validation of Fabric capacity state during workspace provisioning. Useful for non-production environments where capacity may be paused."
  default     = true
}