fix: render SOVD resources for nested entity types

[bburda]

Summary

Subcomponent and subarea entities (served through the components and areas API namespaces) expose the full SOVD resource set, but the UI only branched on type === 'component' / type === 'area'. Nested entities fell through to a bare header and the "No detailed information available for this entity." fallback, were filtered out of search, and rendered the wrong breadcrumb icon.

This change treats 'subcomponent' like 'component' and 'subarea' like 'area':

• EntityDetailPanel: the resource-count prefetch and fetchEntityData, the tab bar / panel render branch, the header icon/background helpers, and the getEntityTypeForApi mapping.
• Breadcrumb segments now resolve their entity type from the loaded tree (findNode) instead of position-based inference, so nested types and deeper hierarchies get the correct icon. getBreadcrumbIcon gains subcomponent / subarea cases.
• SearchCommand: getEntityIcon / getEntityColorClass and the result grouping now include subcomponent / subarea, so they are findable.

Store-side refresh routing already maps both types through the shared NODE_TYPE_TO_RESOURCE map on main.

---

Issue

• closes Subcomponent entities render no resource tabs in detail panel #74

---

Type

• Bug fix
• New feature
• Breaking change
• Documentation only

---

Testing

• EntityDetailPanel.test.tsx mounts the panel with selectedEntity.type === 'subcomponent' and 'subarea': the subcomponent renders the resource tab set and prefetches counts as components; the subarea renders the area panel and prefetches counts as areas. Both assert the "No detailed information available" fallback is absent.
• Full suite: npm test (414 passed).
• npm run lint and npm run typecheck are clean.
• npm run build succeeds.

---

Checklist

• Breaking changes are clearly described (and announced in docs / changelog if needed) - none
• Linting passes (npm run lint)
• Build succeeds (npm run build)
• Docs were updated if behavior or public API changed - no docs change needed

[Copilot]

Pull request overview

Fixes the entity detail view so subcomponent entities render and fetch SOVD resources the same way as component entities, aligning UI behavior with how the gateway serves subcomponent resources (via the components API namespace).

Changes:

• Map subcomponent → components for refresh and API entity-type routing.
• Treat subcomponent as a component in EntityDetailPanel so the resource tab bar renders and resource counts/data are fetched.
• Add a regression test ensuring subcomponents prefetch counts as components and render the full resource tab set.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/lib/store.ts	Ensures Refresh re-fetches subcomponents using the components API type mapping.
src/components/EntityDetailPanel.tsx	Enables resource fetching + tab rendering + header styling for subcomponent entities.
src/components/EntityDetailPanel.test.tsx	Adds a regression test covering the subcomponent tab bar and counts prefetch behavior.

[mfaferek93]

A few comments