feat: Add Badge component

[frankieyan]

Short description

This adds a badge component with 3 variants available:

Figma: https://www.figma.com/file/LYlWNzvhMDh907l07mPPQk/Product-Library---Web?node-id=9038%3A280583

PR Checklist

• Added tests for bugs / new features
• Updated docs (storybooks, readme)
• Executed npm run validate and made sure no errors / warnings were shown
• Described changes in CHANGELOG.md
• Bumped version in package.json and package-lock.json (npm --no-git-tag-version version <major|minor|patch>) ref
• Updated all static build artifacts (npm run build-all)

Versioning

New feature: minor

[pawelgrimm]

LGTM! I left some minor comments for you.

Will you be creating a new minor version or are we going to batch this PR with some others?

[pawelgrimm]

Box actually implements classNames under the hood (ref), so this could be simplified:

Suggested change

	<Box {...rest} className={classNames(styles.badge, variantClassName)}>
	<Box {...rest} className={[styles.badge, variantClassName]}>

[pawelgrimm]

💭 I wonder if it would be better to use the variant as the label... I might be having a slow day, but it took me a second to figure out which variant is which 😅

[frankieyan]

I originally wanted to match the mocks, but yeah this would make it easier to understand.

[frankieyan]

Thanks @pawelgrimm! I've addressed your feedback, please have another look 🙏

Will you be creating a new minor version or are we going to batch this PR with some others?

I usually add a changelog entry to next and only bump versions after changes are merged, in case other changes need to go in in the meantime 👍

[pawelgrimm]

🚀

[pawelgrimm]

I usually add a changelog entry to next and only bump versions after changes are merged, in case other changes need to go in in the meantime 👍

I think that's ok, but I wonder if we can refine this process a bit more. After all, it's possible that after merging to master, but before creating the release, someone else merges to master. Then, if you were to push changes to create your release without realizing that additional merged happened, you would end up creating a release that includes changes you hadn't accounted for. Unlikely at the current pace of development, but not impossible 🤔

It would be very nice if we could include some identifier in a PR that specifies the type of version bump and a changelog entry and then have the CI take care of creating and releasing the new version based on the current state of main at the time of your merge 🤩

[frankieyan]

@pawelgrimm Ernesto created an issue here to get the conversation started: #675

Hopefully, we can prioritize an internal DO to tackle this 👍