web: Improve Patterns selector UI

[dgdavid]

In #1112, the Patterns selector was changed to be more consistent with the rest of the UI selection dialogs. However, the core/Selector component used under the hood wasn't ready to handle auto selection. A partial adaptation was made by allowing overriding how it behaves when an option is clicked (see 61b0c0f), but the UI part is being addressed here by

• Improving how the information is layout
• Letting the user know which patterns are auto selected

  • Using a different accent-color for the checkbox.

    After a few attemps, @imobachgs and me decided to go for a white accent color by now since it was the less out of line. We tested using the primary color (too dark, a bit confusing), only the border (quite confusing), using a dotted bottom border (it does not provide too much information nowadays, honestly), a solid square (weird). In any case, this is just an starting point, we can improve these details later, when we have time for playing a bit and/or giving love to the whole UI radio/checkbox.

  • Explicitly adding the "auto selected" text below the checkbox, since a just a different checkbox style (whatever we choose) is not enough for letting the user know that it has been auto selected pattern in a quick way. And no, a tooltip is not a good solution for this use case: it is hidden until the user focus or hover the widget.

Before	After

The "auto selected" text might looks a bit longer, but honestly "auto" does not provide too much value there: auto what? Maybe we can put it in another place (as a label in the bottom right corner of the item. or in the top left. Whatever. In any case, please accept this change as it is unless you find a very strong stopper. As said above, we can (and should) improve this later, when we can invest the deserved time for this kind of things. And, IMHO, the improvement should start in the back-end by allowing the user to get back to the auto selected state. As it is now is ok (I guess) for YaST user, but it quite confusing. Of course, I know that it isn't something trivial.

[dgdavid]

NOTE: this change reveals that this part, the core/Selector styles, can be simplified / improved. Let's wait a bit until selectors are more defined (we're working in new storage selectors that might have impact in such simplification if finally we get rid of storage/device-utils/DeviceSelector.