Enable notification routing with Access Monitoring Rules for Access Plugins

[EdwardDowling]

Description

This ticket is to track the progress of enabling notification routing with Access Monitoring Rules for the remaining Access Plugins.

Task

For some Access Plugins this change only requires that the plugin kinds we wish to support are added to the check in the common/app used by the access plugins. These should work out of the box e.g. Mattermost, slack and discord.

Others like Opsgenie will need additional changes to get working since they don't use the common/app which handles Access Monitoring Rules for them.

Plugins enabled so far

• [x] Slack - #40659
• [x] Mattermost - #42498
• [x] Discord - #42920
• [x] Jira - N/A - No applicable recipients for Jira plugin to be used by AMR
• [x] Pagerduty - #44754
• [x] Opsgenie - #43298
• [x] ServiceNow - #44875
• [ ] msTeams -

Documentation changes needed for each plugin

• [x] Slack - #41012
• [x] Remainder #42919

Frontend changes

• [x] Slack
• [x] Mattermost - https://github.com/gravitational/teleport.e/pull/4645
• [ ] Discord
• [x] Jira - N/A
• [ ] Pagerduty
• [ ] Opsgenie
• [ ] ServiceNow

[kimlisa]

For each new plugin support, we need to add support to the UI. This PR should include all the same changes required (though, there will be some extra changes (noise) as I was trying to improve other related things at the same time, we can ignore those)

When testing ensure that after creating the supported plugin, go to notifications routing rule and:

• default rule for plugin shows up (test the hover tooltip to ensure the copy is related to the supported plugin)
• can create a rule for this supported plugin (while creating, test all the hover tooltips for same reasons as above)