[needs design] A component appearing in the list of components to instantiate that is broken during development should convey that

Overview

Follow-up for 💬 ComponentNotFoundException: Unable to find component Active .

We've also gotten the /canvas/api/v0/config/component API response working again. It now provides the UI with a flag that indicates whether the known component should be available for instantiation (broken: false) or not (broken: true). That should also change the icon in the component list to something conveying brokenness.

— #3470422-26: Handle components provided by ComponentSources IMPLICITLY disappearing: gracefulness when developing SDCs: SDCs may appear/disappear from one request to the next →

Proposed resolution

When a component listed is known to be broken, convey it to the user — which in principle must be a developer (of either an SDC, a block plugin, a code component …):

1. Use a different icon than the "component" icon.
2. Use a different text style, such as "strikethrough":
3. Allow the preview-upon-hover to continue to work, because it conveys that the component is currently broken
4. Disallow dragging this into the editor frame, because creating more broken instances is pointless

User interface changes