Taking the opportunity to remove the `TODO: Compare this with
src/hooks/usePermissionsInvoiceActions.ts:` comments in the app.

I've come to the conclusion that `canFinalize` should check for an
additional permission so i changed it and adapted the related test

…e object details (#2459)

## Context

We're often facing a `maximum-complexity` graphql error when adding more
data to fetch within the invoice details view.

This view works like a huge get, that retrieve all the data at once.
The query became that big that we reached the default complexity limit
(365) and are blocked when needing to extend this page's features.

This PR attempt to fix that by splitting the query into smaller ones.
This improvement does not aims to fix the fragment architecture spread
over all components, unless they affect directly this query.

Note that we cannot not use the same endpoint within the same query
using aliases, as they would still have impact on the same "final" query
complexity.

## Description

The 2 commit changes aims to separate the invoice informations, invoice
`fees` and invoice `invoiceSubscriptions` into 3 separates queries.
- invoice informations: stays into the `getInvoiceDetails`
- invoice `fees`: new `query getInvoiceFees`
- invoice `invoiceSubscriptions`: new `query getInvoiceSubscriptions`

Having them separated and passed as different props allows us to define
specific types for each of them, defined in
`src/components/invoices/types.ts`.

Some `refetchQueries` had to be updated to fetch the correct query
impacting the correct part of the invoice (here related to
`invoiceSubscriptions`)

Some type manual casting could have been removed along the way.

I performed a manual QA on those scenario and they all work for the
different kind of invoices we have (sub, one-off, credit)
- edit fee
- regenerate invoice
- update invoice statuses (payment, ...)

<!-- Linear link -->
Fixes ISSUE-1146

We have a [low severity
CVE](https://github.com/getlago/lago-front/security/dependabot/113) on a
sub deps of cypress.

It's fixed in their `15.0.0` so let's upgrade to the latest.

This `v15` brings the cypress studio and would be great to test it soon!

Other packages needs to be updated to have the CVE totally fixed on our
repo but they are not there yet.

Simple renaming 

I'm working on a new feature that will add fixed fee on the plan.

The current section related to the Subscription fee is named "Fixed fee"
and better to be renamed to prevent conflicts.

## Context

We recently added the possibility to name a wallet transaction.
At the same time, the wallet name was never displayed in the invoice
details at fee level.

## Description

This PR fixes and improve the wallet related fee
- If the wallet name is present, it becomes the fee display name
- if the wallet transaction name is prevent, we concat it with a
"default" string
- Otherwise we define this "default" string only

Fixes ISSUE-1149

## Context

The usage query was caching the first values received, making the drawer
data innacurate.

## Description

Prevent caching of the usage query.

<!-- Linear link -->
Fixes ISSUE-1148

Simple renaming to better match usage and prepare future implementations

## Context

Related to ai-agent feature.

This PR should update the instantiation of graphql to handle
subscriptions.

## Description

I added actioncable because that's the protocol we're using on the
backend side.
I've also split the `init` file to extract links for readability. 

As subscriptions are not used in the app yet, this can be safely merged

## Context

I'm planning to have a whole new Charge accordion for fixed charges.

Those will have some differences with the event-based charges and today,
the only way to implement those change is either by making the charge
accordion API worst or make inner elements to be more "composable".

## Description

This PR starts to "compose" some components of the charge accordion, so
we can create this fixed charges accordion easier later.
The "main" benefit is visible in
`src/components/plans/UsageChargeAccordion.tsx` and in some create form
pages.

I've created a commit per split, and I'll create other PR as here I
think I only split half if the component.

It's a ready a again in readability and size (1116 lines to 739).

Reverts getlago/lago-front#2448