Added 3 improvements to the process of updating the state of an invoice in Odoo, according to the state in DGI:
**For invoices that have been rejected by DGI:**
 - Added logic to automatically notify relevant users when an electronic invoice (CFE) is rejected by the DGI and, as a result, canceled in the system. The goal is to ensure that there is always someone responsible who is informed to correct and resend the receipt.
 - Added logs in the terminal to make the debug easier in case we want to identify rejected invoices. 
 
**Particular case of an invoice that had been rejected by DGI but the user somehow fixes it and then DGI accepts it:** 
- Added logic to verify both DGI state and Invoice state and adjust it accordingly when updating invoice DGI status.
- Make 'Update DGI status' button always visible to be able to adjust invoices states.

**== Context of the Problem ==**

Previously, when Odoo detected that a CFE had been rejected by the DGI, the system proceeded to cancel the invoice automatically. However, this process was carried out silently, without generating any notification. This could mean that if no user or salesperson was actively monitoring the status of the receipts, the cancellation would go unnoticed, resulting in invoices that were never corrected or reissued.
For the case of a previously rejected and then accepted invoice, we always thought that 'Rejected' state in DGI was a definite state and could not suffer any change. But recently it has been a case that this state changed, creating inconsistencies in Odoo invoices states as they appear as cancelled. With these changes, the user can adjust the invoices state by clicking 'Update DGI status' button.



**== Automatic Notification Logic ==**
With the new functionality, every time an invoice is automatically canceled due to a DGI rejection, the system posts a message in the document chatter to report the situation. The logic for determining who is notified is as follows:

_Scenario 1: Invoice with Internal Followers_

- If the canceled invoice has at least one internal follower (an Odoo user), the system will perform the following actions:
- It will post a message in the invoice chatter.
- It will tag (@) all internal followers to notify them directly.


_Scenario 2: Invoice without Internal Followers_

- If the invoice does not have any internal followers, the system will search for a more general but relevant audience to ensure that the notification is addressed:
- It will post a message in the invoice chat.
- It will tag (@) all users who belong to the “Accounting Manager” permission group (technical name: group_account_manager).


Task ODOO: #[1362](https://latam-localizations.odoo.com/web?debug=1#id=1362&cids=1&menu_id=88&action=131&active_id=16&model=project.task&view_type=form)
Task ADHOC: #[54799](https://www.adhoc.inc/odoo//project.task/54799)

Forward-Port-Of: odoo/enterprise#94502

Currently an error occurs when auto-vacuum tries to clean up Withhold wizard which is a transient model but fails because it is still linked with Withhold lines wizard.

**Steps to replicate:**
* Install `l10n_ec_edi` and change company to `EC company`
* Create invoice with customer `EC Company` > Set Payment Method (SRI) > Confirm
* Add Withhold > Document number: `001-001-123456789` > Add lines > Create & Post
* Set system time to future date > Run `Base: Auto-vacuum internal data`.

Refer video [1] for replication steps.

**Error:**
`psycopg2.errors.ForeignKeyViolation:update or delete on table 'l10n_ec_wizard_account_withhold' violates foreign key constraint 'l10n_ec_wizard_account_withhold_line_wizard_id_fkey' on table 'l10n_ec_wizard_account_withhold_line'
`
**Root cause:**
* The error happens because Withhold Wizard [2] is a transient model that gets cleaned up by function [3] after reaching its max hours.
* However, since [2] is linked to Withhold Wizard Lines [4], the cleanup fails, causing the error.

**Solution:**
* Unlink the lines first and then unlink the wizard.

[1]:
https://drive.google.com/file/d/1HethT8tpa3Ez0uwueUuKzW4F7KxEKOv_/view?usp=sharing 
[2]:
https://github.com/odoo/enterprise/blob/2275fe560d5db0b5a21ffbc4d4c66264e4e12601/l10n_ec_edi/wizard/l10n_ec_wizard_account_withhold.py#L20 
[3]:
https://github.com/odoo/odoo/blob/e062c9b5773ed0710503c13627e60f8233fcd0a5/odoo/models.py#L7465-L7497 
[4]:
https://github.com/odoo/enterprise/blob/7ca0635d4c479a956bfae8fb60da8b50362fd99b/l10n_ec_edi/wizard/l10n_ec_wizard_account_withhold.py#L423-L427

sentry-6253783256

Forward-Port-Of: odoo/enterprise#99653