Rename RUN_DAILY and RUN_WEEKLY

On !195 (merged), we found that the naming of the variables for RUN_DAILY and RUN_WEEKLY were named in an unclear manner. These variables are important to help group jobs into a collection to run within a single pipeline execution.

From what I can tell, here's what what policies are run behind those two variables. Everything else seems to run in a RUN_SINGLE pipeline.

Run daily

• Label reminders
• Stage and group label hygiene
• MR migrate legacy labels
• Accepting merge requests
• Move milestone forward
• Discover
• Missed SLO
• Unlabelled issues - only when UNLABELLED_TRIAGE_PACKAGE is also set

Run weekly

• Team triage package
• Missing categories
• Community merge requests - only when $COMMUNITY_TRIAGE_PACKAGE is also set

Proposal

There are currently two different types of triage policies that I group all policies into.

• TRIAGE_PACKAGE - classification of incoming issues and merge requests for a group or project to aid in identifying actionable items for Product and Group/Stage Managers.
• TRIAGE_HYGEINE - label or comment automation to aid in reporting or nudging behavior into desired direction. The daily jobs that don't have packages in the job name fit this category to me.

The job name would be where we can indicate the desired frequency (schedule:daily:reminders:labels or schedule:weekly:packages:community-merge-requests

Steps

1. Create new anchors based on the triage categories (ie triage-package and triage-hygeine) which leverage a different variable.
2. Convert existing jobs to use the new anchors
3. Update the README with the new variables description
4. After merge is completed, update the existing scheduled pipelines variables

I am still getting my bearings and lack the historical context. I don't want to create a change that would be confusing. I also don't have great view of where Triage Packages 2.0 and 3.0 and how the evolution of our policies fit within these categories.

@rymai @godfat @markglenfletcher - What are your thoughts?

/cc @meks