chore: Show only available integrations

[Dschoordsch]

Description

Fixes #9879
Hide Github, Atlassian and Slack integrations if the oauth environment variables are not set.

If a user has integrated with any of these in the past, then this is not changed. They will be able to use the integration until their token expires. This was already the case before. This PR only affects the visibility of the provider rows.

Demo

https://www.loom.com/share/881a214cb5c042aba2f9df3a96f6f190?sid=658c14b3-8343-4d08-ac48-6cec0b67ed6d 🔒

Testing scenarios

• with the oauth variables for Github, Atlassian and Slack unset check
  • Poker scope
  • Standup Your Work drawer
  • Team integrations
  • Meeting timer
• repeat with variables set

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

[rafaelromcar-parabol]

LGTM!

Just one question: what happens if no integration is available? Shouldn't we show something? I think on the video you say some integrations will always be shown there but I think we should allow to disable those too.

[rafaelromcar-parabol]

Also, IMHO this PR would require a full testing round before being released to production.

[Dschoordsch]

what happens if no integration is available? Shouldn't we show something?

I think we should ignore this case. This is only an edge case for private instances. These get support from us in any case, so it's not an issue.

some integrations will always be shown there but I think we should allow to disable those too.

I can add 2 variables to disable Mattermost and MS Teams.

Also, IMHO this PR would require a full testing round before being released to production.

No objection against testing, but it just touches some UI elements, no logic changed. Production should look exactly the same.

[rafaelromcar-parabol]

I think we should ignore this case.

Agreed. I was just curious.

I can add 2 variables to disable Mattermost and MS Teams.

If it's easy and quick, I think you should, but I'll approve the PR without that, as it's not a requirement.

No objection against testing, but it just touches some UI elements, no logic changed. Production should look exactly the same.

I thought it might risk something other than the UI. In that case, go ahead @Dschoordsch !