Improve the retro-compatibility by fixing default set syntax

Expected behavior

When migrating to the 0.10 (in beta for now), we decided to rename the components from the original sib-* to solid-* . We added a layer of retro-compatibility which works well when you decide to use either a sib-display or a solid-display in your app.

What's happening?

However, when there is a set defined in your fields list, it is generated with a solid- prefix even though the base component is a sib-display (not a solid-display). The impacts of that is that it mainly breaks the CSS targeting and the specific behaviours implemented in JS if any.

Steps to reproduce

1. Switch to the beta branch of sib-core
2. Create a sib-display targetting a single resource. You can see the default widgets applied to it are generated using the solid- prefix
3. Create a sib-display targetting a container. You will see that children are properly generated using the sib- prefix but still, the defaults widgets applied to them are using the new solid- prefix

Relevant logs and/or screenshots

Please see the following JSBin for example : https://jsbin.com/hafevaqeze/1/edit?html,css,output

Your Environment

• Library version: Sib-Core Beta version
• Browser name and version: All of them