chore(actions): add icon leads notification for calcite-ui-icons requests

[geospatialem]

Related Issue: #9922

Summary

Add automation to issues when the calcite-ui-icons label is added, where Icon team leads will receive an @ notification via a comment, similar to the new component label automation from the notifyAboutNewComponent script.

cc @allieorth, @arowles

[benelan]

Why are tagging icon designers in a comment instead of assigning them (or the @Esri/calcite-icon-designers team) to the issue? I think designers would be notified either way, but it assigning would reduce noise for the issue author.

Edit: Actually you can't assign a team to an issue. But assigning the individual designer(s) is still an option.

[geospatialem]

Why are tagging icon designers in a comment instead of assigning them (or the @Esri/calcite-icon-designers team) to the issue? I think designers would be notified either way, but it assigning would reduce noise for the issue author.

Edit: Actually you can't assign a team to an issue. But assigning the individual designer(s) is still an option.

If we'd rather assign issues to the team, can alter the automation - the intent was to be similar to our new component and spike complete notifications, where:

• Icon leads would be notified and could review the request
• If the Icon team would like to proceed with the request, they could assign themselves to follow-up with the requestor once the icon(s) are added
• If the Icon team does not wish to proceed with the request, the issue would be closed with a response to the requestor

[benelan]

If we'd rather assign issues to the team, can alter the automation - the intent was to be similar to our new component and spike complete notifications, where:

• Icon leads would be notified and could review the request
• If the Icon team would like to proceed with the request, they could assign themselves to follow-up with the requestor once the icon(s) are added
• If the Icon team does not wish to proceed with the request, the issue would be closed with a response to the requestor

Gotcha. I don't remember why we decided to comment/mention instead of assign in previous workflows. Assigning would notify them as well, and would have the added benefit of reducing noise for the requester and showing up in the designer's list of assigned issues so things don't get lost.

We don't need to make the change in this PR, but it's something worth considering.

[benelan]

👍