CI/CD: Add label automation to Discussions

[crobert-1]

Component(s)

No response

Describe the issue you're reporting

This is being created from discussions around #27456. A lot of issues are being created that would be better suited for discussions, as they're often usability questions. In order to better support discussions we need to be able to add labels to discussions that can ping code owners. Once this is in place we can add a new issue template that will automatically convert questions to discussions.

[crobert-1]

I've been able to take a bit of a look at this and see the status/blockers. We can currently make use of some of the same scripting that we use for issues, such as the add_labels.yml workflow, since there are the same actions in discussions that can trigger workflows.

However, it looks like the current problem is that the gh CLI (and API) does not interface with discussions, which is how we add labels to issues.

The current solution provided by GitHub is to use GraphQL for discussion API. Sources: here, and here.

Documentation reference.

Example queries for adding labels to a discussion: Here, and here.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[mowies]

A nice solution for this could be the addLabelsToLabelable and removeLabelsFromLabelable GraphQL mutations.
Since both issues and discussions are labelable, we could abstract away the difference that way.