Refactor GHAs so that Templates use label-directory.json

[t-will-gillis]

Overview

We are in the process of replacing all references to labels in our workflows from specifying a label name (labelName) to specifying a label key (labelKey) instead. (Refer to issues #6454 and #5205 for the history) We need to extend this to our templates as well.

Details

To accomplish this, we will replace all labels with a single placeholder label on each template- Template Label Placeholder or similar. When an issue is created from a template and this label is found, the correct labels should be applied to the template issue then the Template Label Holder should be removed.

It appears that this functionality can be created within check-labels.js.

Note that templates without the Template Label Placeholder will continue working using the full label names as they have been.

Action Items

• In check-labels.js add functionality to detect the Template Label Placeholder on issue creation, and if so, substitute the correct labels.
• The correct labels should be contained in a comment on the template's md file, then extracted
• Afterwards, the Template Label Placeholder label itself should be removed.
• Perform a test in your own repo that demonstrates that there is no change to the GHA's functionality after making the edits.
• NOTE: before merging, the label for Template Label Placeholder will need to be created.

Resources/Instructions

• Refer to Hack for LA's GitHub Actions (current revision), especially Tips 6, 7, and 8, if you have not already created you personal environment for testing.
• How to Test GitHub Actions
• Additional Notes for GitHub Actions
• This issue is part of the epic Epic: Refactoring GHA - JavaScript files to use common key: value JSON #6454

[t-will-gillis]

Closing issue: after discussion at the Monday meeting 11/25, it was decided that we will not label the templates with labelKey values and use the automation to insert the labelNames. Instead, we will change the template label names directly if needed.