Add support for labels to Fleet's best practice GitOps

[noahtalerman]

Goal

User story
As a Client Platform Engineer (CPE) using Fleet’s best practice GitOps,
I want to manage labels in my GitHub repo
so that I can enforce code review on changes to labels which impact how I scope configuration profiles to my hosts.

Context

• Requestor(s): _____
• Product designer: _____

Changes

Product

• [ ] UI changes: TODO
• [ ] CLI usage changes: TODO
• [ ] REST API changes: TODO
• [ ] Fleet's agent (fleetd) changes: TODO
• [ ] Permissions changes: TODO
• [ ] Outdated documentation changes: TODO
• [ ] Changes to paid features or tiers: TODO

Engineering

• [ ] Database schema migrations: TODO
• [ ] Load testing: TODO

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. [ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
2. [ ] QA (@____): Added comment to user story confirming successful completion of QA.

[noahtalerman]

FYI @nonpunctual

[rachaelshaw]

@zayhanlon this didn't get designed within the 3-week drafting timeline, bringing back to Feature Fest

[spokanemac]

@noahtalerman As we add more functionality for software deployment based on labels, we should consider bringing this functionality into gitops.

[noahtalerman]

@spokanemac agreed.

I just added the ~feature-fest label if so we remember to consider weighing this one for next design sprint.