[dashboard] Guard subscribeToStripe against multiple calls

[geropl]

Description

Related Issue(s)

Fixes #16524

How to test

• use https://www.notion.so/gitpod/Rapid-frontend-development-without-a-preview-environment-69d13efd271e4c66b6b33f31bc7bb3e1 to inject this to staging
• create a new org
• go to /billing and signup with Stripe
• note how you end up with one subscription only ✔️
• (yes, no proof, but it's hard to reliably re-create the core issue. If you have ideas, please share! 💡 )

Release Notes

NONE

Documentation

Build Options:

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-gpl-subscription-race.1 because the annotations in the pull request description changed
(with .werft/ from main)

[selfcontained]

I didn't have a chance to test this on staging, as the fe dev header doesn't seem to be working for me there. I had a suggestion for the way we're using state and useEffect() though.

[geropl]

I didn't have a chance to test this on staging, as the fe dev header doesn't seem to be working for me there.

Uh, that's bad, it should!
Did you check if your user was logged in before activating the header? That's required because we limit this capability for security reasons, and the thing I regularly bump into 🙃

[AlexTugarev]

Change look good to me. It worked nicely so far.
Let's verify on staging after merging.

[geropl]

Let's verify on staging after merging.

Did that already. 😉 But yeah, it's cheap enough, let's do it!