…voices (#3820)

## Context

We tried to introduce the uniqueness index on
billing_entity_sequential_id, but we populated this value with
organization_sequential_id, and inherited some old duplicated
organization_sequential_id (invoices created before april 2024)

So now we want to update the historical data to be able to introduce the
uniqueness index

## Description

Added a migration that:
1) updates all invoices related to billing_entity with
document_numbering "per_customer" with duplicated
billing_entity_sequential_id to have billing_entity_sequential_id = nil
2) goes through all billing entities with numbering per entity, finds
invoices with duplicated billing_entity_sequential_id and updates it to
nil, if in the database a value already exist with bigger
billing_entity_sequential_id
3) if latest billing_entity_sequential_id is duplicated - means
something went completely wrong, we want to manually investigate it

Note that just updating all invoices except one with maximum
billing_entity_sequential_id to have nil is easier, but this way we'd
erase a lot of correct data + loose information in case we want to
investigate something, so it was decided to proceed with selective
update

…voices (#3820)

We tried to introduce the uniqueness index on
billing_entity_sequential_id, but we populated this value with
organization_sequential_id, and inherited some old duplicated
organization_sequential_id (invoices created before april 2024)

So now we want to update the historical data to be able to introduce the
uniqueness index

Added a migration that:
1) updates all invoices related to billing_entity with
document_numbering "per_customer" with duplicated
billing_entity_sequential_id to have billing_entity_sequential_id = nil
2) goes through all billing entities with numbering per entity, finds
invoices with duplicated billing_entity_sequential_id and updates it to
nil, if in the database a value already exist with bigger
billing_entity_sequential_id
3) if latest billing_entity_sequential_id is duplicated - means
something went completely wrong, we want to manually investigate it

Note that just updating all invoices except one with maximum
billing_entity_sequential_id to have nil is easier, but this way we'd
erase a lot of correct data + loose information in case we want to
investigate something, so it was decided to proceed with selective
update

…voices (#3820)

We tried to introduce the uniqueness index on
billing_entity_sequential_id, but we populated this value with
organization_sequential_id, and inherited some old duplicated
organization_sequential_id (invoices created before april 2024)

So now we want to update the historical data to be able to introduce the
uniqueness index

Added a migration that:
1) updates all invoices related to billing_entity with
document_numbering "per_customer" with duplicated
billing_entity_sequential_id to have billing_entity_sequential_id = nil
2) goes through all billing entities with numbering per entity, finds
invoices with duplicated billing_entity_sequential_id and updates it to
nil, if in the database a value already exist with bigger
billing_entity_sequential_id
3) if latest billing_entity_sequential_id is duplicated - means
something went completely wrong, we want to manually investigate it

Note that just updating all invoices except one with maximum
billing_entity_sequential_id to have nil is easier, but this way we'd
erase a lot of correct data + loose information in case we want to
investigate something, so it was decided to proceed with selective
update