feat(notification/teams): add teams notification

[sranka]

Closes #17939

This PR adds support for Microsoft Teams in InfluxDB notification endpoints and notification rules. It depends on influxdata/flux#2866 that introduces a new teams package to send notifications.

What is in this PR

• implementation and tests of teams endpoint and rule
• swagger updated with teams notification rule and endpoint
• updated UI to use the new swagger + new UI for teams endpoint and rule:
  • Create/Edit Telegram Notification Endpoint
    
  • Create/Edit Telegram Notification Rule
    
  • MS Teams Notification (displayed in https://messagecardplayground.azurewebsites.net/ )
    

What is not in this PR

• teams endpoint and rule in =pkger=
• new UI tests

• CHANGELOG.md updated with a link to the PR (not the Issue)
• Well-formatted commit messages
• Rebased/mergeable
• Tests pass
• http/swagger.yml updated (if modified Go structs or API)
• Documentation updated or issue created (provide link to issue/pr)
• Signed CLA (if not already signed)

[sranka]

The PR could be merged after #18218, small conflicts are expected.

[glinton]

can you split this into two prs (front/back-end) or feature flag the front-end code as it tends to be deployed first

[sranka]

@glinton ... sure, can you please first

• take back or help with the (f67c3a1) telegram notifications into master. I could possibly do it, but I would need some instructions or code pointers to know of how to name or add a feature flag part, I have a lot of conflicts herein that are now hard to resolve. Teams and telegram notifications change the same files and this PR was done on top of existing telegram changes. Teams must be finished first.
• approve fix(endpoints): do not reset organization's secrets when an endpoint is created or updated #19082 , it fixes a major defect in the management of endpoints

[glinton]

take back or help with the (f67c3a1) telegram notifications into master

I'm not certain why that was reverted, so i don't want to un-revert it. My guess is that you'll need to split up that work into 2 prs also, one for the backend code, and one for the front for the same reasons as mentioned above. Reach out to those involved in the revert if you'd like to learn more.

approve #19082

I commented on the pr, but can you add tests to show the behavior described and that the new code fixes that. otherwise it looks like a sane change

[sranka]

@glinton ... I have to wait herein for the telegram to be re-introduced back into master, the other way would be painful. I changed this PR to draft because of it.

[sranka]

@glinton ... this type of notification can be now enabled with a feature flag "notification-endpoint-teams", the implementation follows already approved #19135

[glinton]

go code looks good. I'll let someone with more front-end experience approve the pr after the front-end code is reviewed

[sranka]

This PR cannot be approved and merged anymore, it contains both UI and server part that are in now different repositories. Two PRs are required now.