fix(entitlements): Fix various bugs (#4063)
- [x] wrong API permissions used in controllers
- [x] fix view to ignore deleted entitlements
- [x] fix empty privilege in serializer

update changed scope (#3869)
## Context
Update the scope definition for migration

Revert "chore(organization): Not null organization_id" (#3838)
Reverts #3687.
We want to exclude that from the `1.30` self-hosted release.
Will be included on the `1.31` release.

fix(bug): rescue BaseService::ThrottlingError when calculating Custom… (
#3653)
### Problem
`::Invoices::CustomerUsageService` can raise
`BaseService::ThrottlingError` when `apply_taxes` is `true` and
`customer_provider_taxation?` is `true`.
If the controller does not handle this, the user will receive a 500
error.
This PR does not fix the throttling error because its out of our
control, but inform the user to try again later in a nicer way than a
error 500.
#### Sentry error
https://lago.sentry.io/issues/6336411980/?project=6370067
##
### Steps to reproduce
Have an organization with Anrok provider configured
Have a invoice for an Anrok customer
call api GET `customers/<customer_external_id>/current_usage`. 
Apply taxes is `true` by default.
The ThrottlingError may be raised and return a 500 error.
##
### Result
With the rescue in place, the user would get a response like this when
ThrottlingError happens
```
{
"status" => 429,
 "error" => "Too Many Provider Requests",
 "code" => "too_many_provider_requests",
 "error_details" => { 
      "provider_name" => "anrok",
      "message" => "Service anrok is not available. Try again later."
  }
}
 ```

feat(console): Add `deadjobs_summary` helper (#3651)
Going through your dead queue can be painful if one jobs failed a lot.
You might miss more important jobs.
```
lago-api(dev)> deadjobs_summary
=>
{"Clock::ConsumeSubscriptionRefreshedQueueJob" => 7044,
 "Clock::ProcessAllSubscriptionActivitiesJob" => 14,
 "Clock::FreeTrialSubscriptionsBillerJob" => 1,
 "Clock::RefreshDraftInvoicesJob" => 1,
 "Clock::ActivateSubscriptionsJob" => 17,
 "SendHttpWebhookJob" => 9,
 "SendWebhookJob" => 29,
 "PaymentProviderCustomers::StripeCheckoutUrlJob" => 1,
 "Clock::SubscriptionsToBeTerminatedJob" => 2,
 "Clock::ComputeAllDailyUsagesJob" => 1,
 "Clock::TerminateEndedSubscriptionsJob" => 1,
 "Subscriptions::OrganizationBillingJob" => 1}
```

Fix(multientities): return be sequential id (#3616)
## Context
In order to switch to invoice numbering generation via billing_entities,
invoices should have billing_entity_sequential_id populated. that's why
we're updating:
1) when generating invoice's organization_sequential_id, put the same
value to the billing_entity_sequential_id
2) when switching on org from per_customer to per_organization, fulfil
billing_entity_sequential_id as well as organization_sequential_id
## Description
- Added job to fulfil billing_entity_sequential_id on invoices
- updated sequential_id generation to also fill
billing_entity_sequential_id with the generated value
- updated service responsible for sequential_id generation when
switching document numbering on organization

chore(organization): Add organization_id to dunning_campaign_threshol…
…ds table (#3625)
## Context
This PR is part of the epic to add `organization_id` on all tables of
the application
## Description
The current one is adding the field to the `dunning_campaign_thresholds`
table.
For now the field allows null values. A job to back-fill it has been
added.
In a later pull request the not null constraint will be added

chore(organization): Add organization_id to charge_taxes table (#3583)
## Context
This PR is part of the epic to add `organization_id` on all tables of
the application
## Description
The current one is adding the field to the `charges_taxes` table.
For now the field allows null values. A job to back-fill it has been
added.
In a later pull request the not null constraint will be added

fix(docker): Add psql dependency (#3561)

fix(docker): Add psql dependency (#3561)