[Contributor docs/ADR] Before component deprecation

[tbenning]

Adding new docs to create a better process for what steps to take before component deprecation.

Problem

• Internally, we don't have a clear process for how to decide that we want to deprecate a component
• Externally, consumers will use or ask about components that we have tentatively decided to deprecate, but we have no spent the engineering effort to deprecate in a major release.

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5b61769

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	95.58 KB (0%)
packages/react/dist/browser.umd.js	95.97 KB (0%)

[lesliecdubs]

Left a few comments for thought!

Are you actively looking for Primer engineer feedback at this stage of the doc? If so, I can help boost visibility to get you some more reviews, if you're ready for that.

[lesliecdubs]

I wonder if seeking consensus is the best model for decision-making here, as it could slow down our tempo 🤔 I know the GitHub way is to aim for a "consult and decide" model; how might we put that model into action here?

[lesliecdubs]

Is there a way to do this without requiring live/meeting-based participation in order to support our async culture / distributed teammates?

[github-actions]

Hi! This pull request has been marked as stale because it has been open with no activity for 60 days. You can comment on the pull request or remove the stale label to keep it open. If you do nothing, this pull request will be closed in 7 days.