## Context

This PR is part of [upgrading
Stripe](#3300) (clients + API
version).

## Description

This is extracted from #3300. 

**You cannot update the `api_version` of an existing WebhookEndpoint**.
You must create a new WebhookEndpoint with the new version and delete
the old one once you migrated. This is the best way to not have any
downtime.

https://docs.stripe.com/webhooks/versioning

It means to set the version for all our customers, we'll need to
recreate the endpoint for all organization. It's fine but I'd rather
upgrade to a more recent version before we enforce it in the webhook.

* Replace `PaymentProviders::StripeService.new.refresh_webhook` by
dedicated `RefreshWebhookService`
* Tried to make `PaymentProviders::StripeService.create_or_update` a
little clearer as secrets cannot be updated

## Context

See #3300

## Description

When upgrading stripe versions, your app will continue to receive older
version of the webhook for while (exactly like when running rails db
migrations) so all modifications made to webhooks processing need to be
backward compatible.

We run tests with all versions to ensure compat'.

**Make sure you hide whitespace to review!**

![CleanShot 2025-06-09 at 11 07
07@2x](https://github.com/user-attachments/assets/ff46f79c-1ddd-4f13-8e9b-d870de7b9b7d)

## Context

See #3300

## Description

When upgrading stripe versions, your app will continue to receive older
version of the webhook for while (exactly like when running rails db
migrations) so all modifications made to webhooks processing need to be
backward compatible.

We run tests with all versions to ensure compat'.

**Make sure you hide whitespace to review!**

![CleanShot 2025-06-09 at 11 07
07@2x](https://github.com/user-attachments/assets/ff46f79c-1ddd-4f13-8e9b-d870de7b9b7d)

## Roadmap Task

👉  https://getlago.canny.io/feature-requests/p/{{FEATURE_SLUG}}

## Context

Everything you need to know:
#3300

## Description

From now on, all Stripe API calls made by lago will be made using the
API version `2025-04-30.basil`.

Lago users can continue to use Stripe in any versions they like on their
side. They can keep their stripe account configured with any version
too.

Until now, Lago would use the user's account version, which could lead
to different response shape, breaking the code. It never did yet because
we use very core and simple feature of Stripe, but it could in the
future.

## Roadmap Task

👉  https://getlago.canny.io/feature-requests/p/{{FEATURE_SLUG}}

## Context

Everything you need to know:
#3300

## Description

From now on, all Stripe API calls made by lago will be made using the
API version `2025-04-30.basil`.

Lago users can continue to use Stripe in any versions they like on their
side. They can keep their stripe account configured with any version
too.

Until now, Lago would use the user's account version, which could lead
to different response shape, breaking the code. It never did yet because
we use very core and simple feature of Stripe, but it could in the
future.