Do not remove/add project from billing when updating stack

[knolleary]

Description

As a: user

I want to: update my project stack without being invoiced

So that: I don't get multiple invoices when performing basic admin tasks on my projects

---

Under the covers, our implementation of updating a project stack involves:

• suspending the project
• changing the stack pointer
• starting the project

When billing is enabled, the suspend step causes us to remove the project from the team subscription on stripe. It then gets re-added when the project is restarted.

This triggers invoices from Stripe which is unexpected for the user and may lead them to think they are being charged extra/incorrectly etc.

Whilst it is correct to remove the project from stripe when the project is suspended, there are cases like this where we know the project will be resumed immediately. As such, we should pass in a flag to the suspend call to say this is a 'temporary' suspend. The billing logic can then use that flag to skip removing from the subscription.

We also need to be able to resume the project without having it readd to stripe - we don't want to end up double charging. Whether it this is done by a similar flag passed to the start call, or if we need to track the state more persistently, I'm not sure without stepping through the logic we currently have.

Which customers would this be availble to

All

Acceptance Criteria

• Can update project stack without interfering with billing

[Pezmc]

This is working on https://github.com/flowforge/flowforge/tree/feat-1598-stack-change-without-billing but will conflict with #1610 so am addressing that first.

[Pezmc]

This is now deployed to staging and ready to be verified there.