chore(PPDSC-2512): component statuses

[mstuartf]

PPDSC-2512

What

1. Background - why this is needed

• Some component statuses on the doc site are out of date (e.g. deprecated components listed as supported)

2. What did you do
3. What does the reviewers should expect

• Pipeline should fail if site and src component statuses do not match (e.g. https://app.circleci.com/pipelines/github/newscorp-ghfb/newskit/5137/workflows/495e36bb-7ce4-4e53-8059-4af3269f4051/jobs/106833)
• Site component statuses should match src
• Component status badge styling should match ticket

I have done:

• Written unit tests against changes
• Written functional tests against the component and/or NewsKit site
• Updated relevant documentation

I have tested manually:

• The feature's functionality is working as expected on Chrome, Firefox, Safari and Edge
• The screen reader reads and flows through the elements as expected.
• There are no new errors in the browser console coming from this PR.
• When visual test is not added, it renders correctly on different browsers and mobile viewports (Safari, Firefox, small mobile viewport, tablet)
• The Playground feature is working as expected

Before:

After:

Who should review this PR:

How to test:

[newskit-engineering]

You can preview these changes on:
Documentation Site: http://ncu-newskit-docs.s3-website-eu-west-1.amazonaws.com/ppdsc-2512-component-statuses
Storybook: http://ncu-newskit-docs.s3-website-eu-west-1.amazonaws.com/ppdsc-2512-component-statuses/storybook

[JohnTParsons]

Code looks ok but ci/circleci: test_unit_docs is failing

[mstuartf]

Code looks ok but ci/circleci: test_unit_docs is failing

@JohnTParsons yep, I started with a test script and pushed to verify that it would fail (the PR is still in draft). Just checking everything over and will move to ready_for_review shortly.