Rebrand the component-library repo as va-design-system

[bkjohnson]

Description

The Design System team currently has two main repos:

• component-library
• vets-design-system-documentation

Additionally, formation (the older npm package with CSS and some global JS) is in the veteran-facing-services-tools repo.

Our policy so far has been to put documentation issues & requests for components into the documentation repo, with other Design System-related requests going into the va.gov-team repo.

The goal with this ticket is to have all Design system code, documentation, and issue tracking in a single repo

Acceptance criteria

• Archive the older design-system repo (:upside_down_face: )
• Create Design System issue templates in this repo
• Migrate issues from vets-design-system-documentation to this repo
• Migrate issue & PR labels from vets-design-system-documentation to this repo
• Rename this repo to va-design-system (or something similar)
• Create new package for design.va.gov code in packages/documentation (or docs, etc.)
• Move design.va.gov deployment into this repo
  • This should happen after Migrate design site deployment from CircleCI to GH Actions va.gov-team#33568 is complete
• Move jekyll setup from vets-design-system-documentation into the monorepo package destination
  • Do we want to preserve git history?
  • This can optionally be done over several PRs to make things easier to review
• Archive vets-design-system-documentation