feat(blueprints): add incentives to update blueprints in the service settings

[rmnbrd]

feat(blueprints): add incentives to update blueprints in the service settings

This PR introduces 2 new incentives to update the blueprint, when a new blueprint version or a new major version is available.

Screenshots / Recordings

Testing

• Changes tested locally in the relevant Console's pages and Storybooks
• yarn test or yarn test -u (if you need to regenerate snapshots)
• yarn format
• yarn lint

PR Checklist

• I followed naming, styling, and TypeScript rules (see .cursor/rules)
• I performed a self-review (diff inspected, dead code removed)
• I titled the PR using Conventional Commits with a scope when possible (e.g. feat(service): add new Terraform service) - required for semantic-release
• I only kept necessary comments, written in English (watch for useless AI comments)
• I involved a designer to validate UI changes if I am not a designer
• I covered new business logic with tests (unit)
• I confirmed CI is green (Codecov red can be accepted)
• I reviewed and executed locally any AI-assisted code

[codecov]

Codecov Report

❌ Patch coverage is 81.81818% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 46.99%. Comparing base (c7034cc) to head (6fdc1c2).

Files with missing lines	Patch %	Lines
...rm-general-settings/terraform-general-settings.tsx	81.81%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           staging    #2821      +/-   ##
===========================================
+ Coverage    46.97%   46.99%   +0.01%     
===========================================
  Files         1263     1263              
  Lines        27073    27084      +11     
  Branches      7897     7902       +5     
===========================================
+ Hits         12718    12728      +10     
  Misses       12180    12180              
- Partials      2175     2176       +1     

Flag	Coverage Δ
unittests	46.99% <81.81%> (+0.01%)	⬆️

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.

[Copilot]

Pull request overview

This PR adds new “blueprint update” incentives inside the Terraform service general settings, surfacing when a service’s blueprint has a newer version and/or a newer major version available, and wires the CTA to the existing blueprint update flow route.

Changes:

• Display a “New major version available” signal when the blueprint update payload contains new_major_versions.
• Display a callout prompting to update when is_up_to_date is false, with an “Update” CTA that navigates to the blueprint update flow.
• Add unit tests for the new signals/CTA behavior and bump qovery-typescript-axios to a newer version.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
yarn.lock	Updates the lockfile for the qovery-typescript-axios bump.
package.json	Bumps qovery-typescript-axios dependency version.
libs/domains/service-settings/feature/src/lib/service-general-settings/terraform-general-settings/terraform-general-settings.tsx	Adds blueprint update signals + navigation CTA in Terraform general settings.
libs/domains/service-settings/feature/src/lib/service-general-settings/terraform-general-settings/terraform-general-settings.spec.tsx	Adds tests covering the new blueprint update signals and navigation behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.