fix(collector): show per-signal stability levels and remove generic fallback description

[aabhinavvvvvvv]

Summary

Closes #375

• Replace the single stability badge on collector list cards with a full breakdown of all stability levels and their associated signals (e.g., [stable] logs, metrics, traces / [alpha] profiles)
• Remove the generic "Browse technical details and configuration options for this component." fallback text — cards with no description now render blank instead

Screenshots

Before:

After:

[netlify]

✅ Deploy Preview for otel-ecosystem-explorer ready!

Name	Link
🔨 Latest commit	1ed0dcc
🔍 Latest deploy log	https://app.netlify.com/projects/otel-ecosystem-explorer/deploys/6a0314d55e9ab7000866eb3c
😎 Deploy Preview	https://deploy-preview-427--otel-ecosystem-explorer.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[vitorvasc]

Hi @aabhinavvvvvvv! Could you add some screenshot examples to the description showing the before and after? 🙌🏼

[Copilot]

Pull request overview

Updates the Collector components list UI to better reflect per-signal stability metadata and to avoid showing a generic description when component descriptions are missing.

Changes:

• Only render a component description paragraph when comp.description is present (removes the generic fallback text).
• Replace the single stability badge on list cards with a per-stability-level breakdown showing associated signals.

[aabhinavvvvvvv]

@vitorvasc I've added screenshots and resolved copilot's comments

[vitorvasc]

Thanks @aabhinavvvvvvv. I'll get back to it as soon as possible.

[vitorvasc]

Hi @aabhinavvvvvvv, thanks for your patience!

There are two things I'd like us to address before merging:

1. Multi-stability components will render two (or more) rows on the card, and things could messy in this scenario. It's worth testing alternatives for how we can show that information before merging, such as using tooltips or collapsible elements.
2. Signal names such as logs_to_metrics or traces_to_traces seem too "raw" for a card surface, can we normalize these to human-readable names? I'd say that could even mean stripping the _to_* suffix, but I'll ask for a second opinion from a Collector maintainer here. @mx-psi, any thoughts on this?