Make it more obvious how to add an upvote

[atopal]

In the issues, it's not immediately clear that you should upvote the issue itself, especially since the descriptions have gotten significantly longer. We should add one upvote to all features to make it easier and more obvious to tell what we expect people to do when we say "upvote". Since all features would get one upvote, it would even out between them again.

[foolip]

This makes sense to me. It makes it one click to upvote instead of click-move-click to find the thumbs up reaction.

[rviscomi]

Here's a proof of concept of using inline images to convey the browser support info more compactly.

Taking #380 for example, which has this browser support list:

Chrome 80 (Feb 4, 2020)
Chrome Android 80 (Feb 4, 2020)
Edge 80 (Feb 7, 2020)
Firefox: not supported
Firefox for Android: not supported
Safari: not supported
Safari on iOS: not supported

We can show something like this instead:

• Chrome 80 (Feb 4, 2020)
• Chrome Android 80 (Feb 4, 2020)
• Edge 80 (Feb 7, 2020)
• Firefox: not supported
• Firefox for Android: not supported
• Safari: not supported
• Safari on iOS: not supported

The images were sourced from the inline SVGs in baseline-status and saved as external resources in this dir.

[foolip]

@rviscomi yes that's great! Do you think we could also include the appropriate Baseline icon?