Don't open new Jira issue when GitHub discussion is created by a team member (OSOE-390)

[sarahelsaig]

Currently the create-jira-issues-for-community-activities action creates a new Jira issue whenever someone opens a new discussion on GH, even if that someone is one of us. (e.g. https://lombiq.atlassian.net/browse/OCC-92) It would be better to avoid that if the discussion creator was a team member who makes announcements. I think we could use one or both of these techniques to get a list of team members:

• Query the "Collaborators and teams" for the repository, select the members with write access.
• Add an ignore-discussion-author input to the action and list the team members who'd write announcements (usually the project leader) in the repository's workflow that invokes the action. This has to be manually maintained, but it's practical when the repository might have external contributors that wouldn't have Jira access (e.g. in OCC).

Jira issue

[Piedone]

We don't open issues for reviewing PRs that are related to a Jira issue, because there the review is determined by the issue. However, discussions aren't related to Jira issues, and need attention from the project maintainer in the same way a discussion opened by a third-party does. If the maintainer doesn't know about it, it'll go without responses too. Thus, why would we exclude them?

[sarahelsaig]

Seems overly cautious to me, but I tend to leave my GH notifications settings very broad so I get a notification anyway. I guess that's up for taste.

However I still think adding an ignore-discussion-author would be a good idea and it should include at least the project leader. This way the action won't generate useless issues when we make announcements.

[Piedone]

We can have an ignore list of authors, yes.

[sarahelsaig]

Ok, updated the description accordingly.