feat(blueprints): restore Terraform settings for Terraform-based Blueprint services

[rmnbrd]

Summary

#2965 hid the Terraform-specific settings pages for every Blueprint service. This PR brings back Terraform configuration and Terraform arguments in the service settings sidebar for Terraform-based Blueprint services. Users can again tune the engine and version, backend, execution credentials, timeout, Dockerfile fragment, and per-command arguments.

• Terraform Blueprint sidebar: General → Blueprint configuration → Terraform configuration → Terraform arguments → Resources → Advanced settings → Danger zone
• Helm-based Blueprint services are unchanged and don't show these links.
• Regular (non-Blueprint) Terraform services are unchanged.

The routes for both pages were never removed, so this PR only changes the sidebar in service-settings-layout.tsx.

Screenshots

Settings sidebar of a Terraform Blueprint service (AWS RDS MySQL)

Terraform configuration

Terraform arguments

Screen recording: walkthrough.mp4

Test plan

• service-settings-layout.spec.tsx: the Terraform Blueprint test now checks that both links are shown. The Helm Blueprint test checks that they stay hidden.
• Checked manually on a local console against a Terraform Blueprint service: both pages load with the service's current values.

🤖 Generated with Claude Code

---

Summary by cubic

Restores the Terraform configuration and Terraform arguments links in the settings sidebar for Terraform-based Blueprint services, which were previously hidden for all Blueprint services.

• Terraform-based Blueprint services now show both pages between Blueprint configuration and Resources.
• Helm-based Blueprint services and regular services are unchanged.

^{Written for commit cccf6cd. Summary will update on new commits.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit cccf6cd

Command	Status	Duration	Result
nx run console:build --parallel=3 --configurati...	✅ Succeeded	1m 15s	View ↗
nx affected --target=test --parallel=3 --config...	✅ Succeeded	42s	View ↗
nx affected --target=lint --parallel=3	✅ Succeeded	2m 27s	View ↗
nx-cloud record -- yarn nx format:check	✅ Succeeded	2s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-10-06 13:29:42 UTC

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.55%. Comparing base (b850f41) to head (cccf6cd).

Additional details and impacted files

@@             Coverage Diff             @@
##           staging    #3081      +/-   ##
===========================================
+ Coverage    52.25%   56.55%   +4.30%     
===========================================
  Files         1378       43    -1335     
  Lines        30644     1441   -29203     
  Branches      9003      469    -8534     
===========================================
- Hits         16013      815   -15198     
+ Misses       12060      442   -11618     
+ Partials      2571      184    -2387     

Flag	Coverage Δ
unittests	56.55% <ø> (+4.30%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.