Try to intelligently render components for attribute types that are not defined here

[goldenapples]

Because Shortcake allows developers to extend the built-in attribute types with custom input types, it is to be expected that there will be many attribute inputs that do not have Gutenberg representations. This poses a usability challenge for editorial workflows that have gotten used to the user-friendliness of custom-defined inputs.

While it is possible, at first, to fall back to a text input field for all unknown attribute types, it will be important to enhance this as soon as possible:

• From the beginning of development here, there should be a way for developers to extend the basic text field class with a component more appropriate for the display they want to use for the custom attribute type in question.

• It might be possible to have a translation layer which checks the global sui.views for any attribute field views not known here, and renders the backbone view wrapped in a React component, to preserve as much as possible backwards compatability.