Warnings in console cost a lot

Expected behavior

When a developer uses a sib-display tag instead of a solid-display, it should write a warning in the console. If the developer uses 10 of them, it should still write only one warning.

What's happening?

When a developer uses 10 sib-display tag instead of a solid-display, it writes 10 warnings in the console.

A warning costs quite a lot in term of performances: one is between 0.2 and 1ms. We should reduce them in order to improve performances.

Relevant logs and/or screenshots

For FNK, at loading time, we have around 500ms of time used displaying warning (300). If we click on a circle, it goes up to 1500ms (1600).

If we limit the warnings to one for each component, we go down to 18ms at loading time, and 22 after 1 click on a circle.