Introducing Category Labels

[jezogwza]

With the design evolution, the original "component/xxx" labels have become stale. At the same time, we are trying to be more fine grained in identifying the outstanding work & priority.

We have dropped the component labels and are introducing the following new categories in order of importance for all open, unassigned issues:

Label	Description
1-Core	Relates to airshipctl core components (i.e. go code)
2-Manifests	Relates to manifest/document set related issues
3-Container	Relates to plugin related issues
4-Gating	Relates to issues with Zuul & gating
5-Documentation	Improvements or additions to documentation
6-upstream/project	Requires a change to an external project. The "project" should be the project name (e.g. clusterctl, helm, metal3, etc.)
7-NiceToHave	Relates to issues of lower priority that are not part of critical functionality or have work arounds. When these get pulled in, should get one of the above category labels

References:
https://github.com/airshipit/airshipctl/labels
1-Core Relates to airshipctl core components (i.e. go code)
2-Manifests Relates to manifest/document set related issues
3-Container Relates to plugin related issues
https://github.com/airshipit/airshipctl/labels/4-Gating
5-Documentation Improvements or additions to documentation
https://github.com/airshipit/airshipctl/labels/6-upstream/helm
https://github.com/airshipit/airshipctl/labels/6-upstream/metal3-io
7-NiceToHave Relates to issues of lower priority that are not part of critical functionality or have work arounds

All open treasuremap issues are labeled as 2-Manifests
https://github.com/airshipit/airshipctl/treasuremap/2-Manifests