Feat/terminate orga add orga id credit notes

[ancorcruz]

Context

This change makes it easier and more feasible to implement a mechanism for terminating an organization and deleting all its data. By explicitly associating CreditNote records with Organization, we improve data consistency and simplify tenant-scoped deletions.

Beyond the primary goal, this change also benefits the multi-tenant application in several ways:

• Improves data integrity by making the organization-tenant relationship explicit.
• Enables more efficient queries and filtering at the organization level.
• Aligns CreditNote with other models that are already explicitly tied to Organization.

Description

• Added an organization_id column to credit_notes, with an index and foreign key constraint.
• Updated CreditNotes::CreateService to set organization_id when creating a CreditNote.
• Refactored event tracking to reference credit_note.organization_id directly.
• Updated specs to assert the presence of organization_id.

Impact

• Existing CreditNote records will need backfilling (handled separately if needed).
• Queries can now leverage organization_id for better performance.
• Future work on organization deletion is now more straightforward.

Next up:

• backfilling
• marking the column not_null

[nudded]

I think every statement needs to be its own migration.

[ancorcruz]

okay, not sure about this, strong migrations has not complained so far.... why it needs to be in various migrations?

[nudded]

the reason would be to limit the amount of statements that are executed without transaction. I don't think it matters a lot, but I believe it's good practice to split the migration into multiple files :)