## Context

This PR follows #3747

Deleting a charge in a plan with a large number of override can cause
Timeout error or lead to a memory error on Redis.

The main reasons are:
- The service will enqueue one job per child charge
- In the service, the soft deletion is done using `discard_all` witch is
not scalable as it is using a DB call per record...


## Description

This PR is refactoring the logic to enqueue only one job responsible of
the soft deletion of all child charges.
The filter deletion is also done by replacing `discard_all` calls with
`update_all(deleted_at:)`

Note: The same logic will have to be applied to both update and creation
of child charges

## Context

This PR follows #3747 and
#3765

Create a new charge in a plan with a large number of override can cause
Timeout error or lead to a memory error on Redis.

The main reasons is that the service will enqueue one job per child plan


## Description

This PR is refactoring the logic to enqueue only one job responsible of
the creation of all child charges.

Note: The same logic will have to be applied to the update of child
charges

## Context

Deleting a billable metric attached to a lot of charges and filters may
lead to a Timeout error because:
- The soft deletion of sub-resources is done synchronously
- It is using `discard_all` witch is not scalable as it is using a DB
call per record...

## Description

This PR is moving the filter deletion to a dedicated job and is
replacing `discard_all` calls with `update_all(deleted_at:)`

## Context

This PR follows #3747

Deleting a charge in a plan with a large number of override can cause
Timeout error or lead to a memory error on Redis.

The main reasons are:
- The service will enqueue one job per child charge
- In the service, the soft deletion is done using `discard_all` witch is
not scalable as it is using a DB call per record...


## Description

This PR is refactoring the logic to enqueue only one job responsible of
the soft deletion of all child charges.
The filter deletion is also done by replacing `discard_all` calls with
`update_all(deleted_at:)`

Note: The same logic will have to be applied to both update and creation
of child charges

## Context

This PR follows #3747 and
#3765

Create a new charge in a plan with a large number of override can cause
Timeout error or lead to a memory error on Redis.

The main reasons is that the service will enqueue one job per child plan


## Description

This PR is refactoring the logic to enqueue only one job responsible of
the creation of all child charges.

Note: The same logic will have to be applied to the update of child
charges

## Context

This PR follows:
- #3747
- #3765
- #3767

Updating a charge in a plan with a large number of override can cause
Timeout error or lead to a memory error on Redis.

The main reason is:
- The service will enqueue one job per child charge


## Description

This PR is refactoring the logic to enqueue only one job responsible of
the updates for all child charges.