[UBP] Remove team specific Stripe APIs from server JSON-RPC API

[andrew-farries]

Description

As part of #12685, several server APIs were generalised to work on user attribution ids as well as team attribution ids:

• [UBP] Add server method to create a stripe customers for an individual user #12753
• [UBP] Add findStripeSubscriptionId method to server #12876
• [UBP] Add getStripePortalUrl method to server #12864
• [UBP] Add getUsageLimit and setUsageLimit methods to server #12767
• [UBP] Add subscribeToStripe server method #12887

With #12942 and #12954, the more specific team-only APIs are no longer used by the dashboard and are safe to remove.

⚠️ #12942 and #12954 need to be deployed first ⚠️

Related Issue(s)

Part of #12685

How to test

Signing up teams and individual users for UBP still works.

Release Notes

NONE

Documentation

Werft options:

• /werft with-preview
• /werft with-payment

[werft-gitpod-dev-com]

started the job as gitpod-build-af-remove-team-specific-stripe-apis.4 because the annotations in the pull request description changed
(with .werft/ from main)

[andrew-farries]

/werft run

👍 started the job as gitpod-build-af-remove-team-specific-stripe-apis.17
(with .werft/ from main)

[jankeromnes]

Hi @andrew-farries! Many thanks for cleaning all these up. 🧹

While testing, I encountered one weird bug. Might be unrelated to your PR (because I see no dashboard changes), but here is what happened:

1. Created a team called "Gitpod [Something]"
2. Upgraded that team to Usage-Based
3. Checked that the Customer Portal worked ✅
4. Tried to change the limit from 100 to 200 credits
5. This seemed to work, but after a refresh I somehow landed in this state:

Setting the limit again to 200, and dismissing the alert, seems to fix it again. But still very confusing.

[jankeromnes]

Then, I tried the same for individual billing:

1. Upgrade to Usage-Based
2. Change the usage limit from 100 to 200
3. Refresh...

🙈 what is going on with these limits?

[jankeromnes]

Many thanks! ✨

Apart from the two really weird but unrelated-looking Usage Limit errors, this works as advertised. 🛹

[andrew-farries]

Those usage limit errors do indeed look very odd. I assume they can also be repro'd in a preview based on main? We should have issues for them if we don't already. Want me to have a look or do you want to do it?

[jankeromnes]

Good point about tracking those in issues @andrew-farries -- also, many thanks for offering 💯 but given that you're on-call, I'm happy to try & repro these from main and file issues about them this afternoon. 👍