Formalize a set of criteria for ‘deprecated’ code that is eligible for removal

[holdenhinkle]

Just capturing the ticket:

Formalize a set of criteria for ‘deprecated’ code that is eligible for removal.

This idea comes from @bosawt in this DS@VA Slack thread - https://dsva.slack.com/archives/C0460N83Y9G/p1668807965749319

Issue Description

What details are necessary for understanding the specific work or request tracked by this issue?

---

Tasks

• [ ] What work is necessary for this story to be completed?

Acceptance Criteria

• [ ] What will be created or happen as a result of this story?

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[holdenhinkle]

To be discussed at the next BE CoP meeting on 12/2/2022.