feat(blueprints): add support for the new displayName property

[rmnbrd]

Summary

Issue: QOV-2232

Updates the Blueprint creation experience to use the new Service Catalog metadata.

• Displays displayName when provided by the catalog, with the existing name formatter as a fallback.
• Groups blueprint cards by their catalog-provided primaryCategory.
• Derives categories dynamically from returned blueprints, so the Console does not maintain a duplicate category registry.
• Falls back to an Other section for catalogs that do not yet provide a category.

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

---

Summary by cubic

Blueprint UI now prefers the catalog's optional displayName over the formatted blueprint name and groups blueprint cards by primary category, falling back to the old label for entries without either.

• Shows displayName in blueprint cards, details panel, configuration view, and step summary.
• Uses displayName as the default service name in the creation flow.
• Includes displayName in catalog search matching.
• Groups blueprint cards by catalog primary category, falling back to "Other" when missing.

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

[nx-cloud]

View your CI Pipeline Execution ↗ for commit cb405c4

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

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

---

☁️ Nx Cloud last updated this comment at 2026-09-04 15:57:23 UTC

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.06%. Comparing base (cf23dce) to head (cb405c4).
⚠️ Report is 2 commits behind head on staging.

Additional details and impacted files

@@             Coverage Diff             @@
##           staging    #2939      +/-   ##
===========================================
- Coverage    50.16%   48.06%   -2.10%     
===========================================
  Files          864      511     -353     
  Lines        21614    13364    -8250     
  Branches      6580     4117    -2463     
===========================================
- Hits         10843     6424    -4419     
+ Misses        8904     5841    -3063     
+ Partials      1867     1099     -768     

Flag	Coverage Δ
unittests	48.06% <100.00%> (-2.10%)	⬇️

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.