feature (#169): add migration badges

[bencodezen]

Netlify Preview

Still not sure about the full list of what we want to include and how to tag things appropriately.

Maybe the badges should only be used next to the bulleted items in each overview section? That way it doesn't seem like the entire thing is broken or that an entire feature is removed?

Also, styles are totally up for feedback / changes. Just iterating along the way!

Closes #169

[NataliaTepluhina]

@bencodezen just my chaotic thoughs

• badges look cool! I'm not sure about the placement - should it be above title, inline or under
• core, directives etc is a bit confusing to me as tbh as it's hard to define the finite list of such categories
• AsyncComponents are breaking too! (current async imports will stop working)

[bencodezen]

@bencodezen just my chaotic thoughs

• badges look cool! I'm not sure about the placement - should it be above title, inline or under
• core, directives etc is a bit confusing to me as tbh as it's hard to define the finite list of such categories
• AsyncComponents are breaking too! (current async imports will stop working)

Yeah I was trying to use the labels that were in the RFCs repo, but I don't think it makes sense to use what's in there. For now, maybe we can start with the following generic badges:

• Breaking
• Removal
• Updated*

• I debated "Major Changes" vs "Minor Changes," but this might be subjective and so I went with something more generic

[phanan]

The Netlify preview is gone for some reason. @bencodezen maybe a rebuild?

[sdras]

These changes make a lot of sense to me, I didn't see anything breaking about your PR about breaking, haha

[sdras]

Looks like there are some merge conflicts and then we're good to go, @bencodezen