Test notify_team_new_comment workflow

[rparadowski]

Description

Goal is to test notify_team_new_comment before adding the same changes to kolibri, studio, ricecooker, kolibri-design-system

Issue addressed

learningequality/kolibri#12567

Addresses #PR# HERE

Before/after screenshots

Changelog

• Description: add notify_team_new_comment workflow
• Products impact: none
• Addresses: Make 'notify_team_new_comment' GitHub action re-usable kolibri#12567
• Components: Affected public KDS component. Do not include internal sub-components or documentation components.
• Breaking: no
• Impacts a11y: no
• Guidance: no applicable

Steps to test

1. Create issue and link it to PR
2. Change default repo branch to the branch you are changing due to https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#issue_comment
3. Post comment in issue.
4. Check if action is executed

(optional) Implementation notes

At a high level, how did you implement this?

Does this introduce any tech-debt items?

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical and brittle code paths are covered by unit tests
• The change is described in the changelog section above

Reviewer guidance

• Is .github repository reference changed to https://github.com/learningequality/.github/tree/main ?

After review

• The changelog item has been pasted to the CHANGELOG.md

Comments

MAKE SURE CHANGE DOES NOT REFER TO FORK!

[rparadowski]

Resutl of testing with https://github.com/rparadowski/.github/tree/12567_issue :

[rparadowski]

Change ference to learningequality/.github/.github/workflows/notify_team_new_comment.yml@main after learningequality/.github#9 is merged