Update GitHub labels and ensure that consistent standards are documented

[jrgriffiniii]

Currently the labels between core component GitHub repositories are quite inconsistent (and some of these are unclear). These should be updated in order to facilitate with onboarding and remove any obstacles from ongoing development labor.

[jrgriffiniii]

A number of these labels seem to have been mistakenly migrated from the deprecation of Waffle.io: https://web.archive.org/web/20190317040044/https://waffle.io/closing-its-doors

[jrgriffiniii]

Labels which are invalid or no longer appropriate (e. g. those relating to workflow status on Waffle, past sprints, or the deprecated cCLA requirements) have been removed.

[jrgriffiniii]

Evaluating the current state of each core component and the associated labels, I am going to please propose that the following common labels be offered:

Label	Description
a11y	Compliance with accessibility (a11y) standards
bug	Unexpected feature behavior or software error
ci	Continuous integration
code-coverage	Coverage of the code base using unit, integration, or automated acceptance test suites
documentation	Documentation in the form of GitHub Markdown, GitHub Wiki, or code comments (e. g. rdoc or Yard)
duplicate
enhancement	Feature improvement or a new feature
invalid
maintenance	A task or action delegated to the Component Interest Group
question	A discussion regarding any aspect of the code base (including documentation or continuous integration)
security	An update addressing a known vulnerability in the code base (or in a dependency)
wontfix

I am still uncertain as to whether or not retaining the labels wontfix, invalid, or duplicate are entirely helpful (as, in all three cases, presumably these GitHub Issues would simply be closed). These would perhaps only be valuable in assessing the status of closed issues which may have been erroneously closed?

[jrgriffiniii]

These should also be configured by default for the GitHub Organization: https://docs.github.com/en/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization