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#98210
Forward-Port-Of: odoo/enterprise#94502

Before this commit:
-------------------
When a user added an existing signature field to a view, Studio automatically assigned the default binary widget.
The expected signature widget did not appear in the widget selection list. As a result, users could not configure the field as a signature input.
<img width="1920" height="938" alt="image" src="https://github.com/user-attachments/assets/35893235-2541-4bd5-a7a5-4feab562acb2" />

Cause:
-----
Studio builds the dropdown of available widgets by computing a [widgetKey](https://github.com/odoo/enterprise/blob/17.0/web_studio/static/src/client_action/view_editor/editors/utils.js#L132) based on the field type.
Because the signature widget did not declare binary as a supported field type, it was always filtered out for fields of type binary. Thus Studio treated the field like any normal binary field and excluded the signature option.

After this commit:
------------------
The signature widget is correctly exposed as a supported widget for fields of type binary.
When adding an existing signature field to the view (with developer mode enabled), Studio now shows signature in the widget list.
<img width="1917" height="934" alt="image" src="https://github.com/user-attachments/assets/079e0a17-ff5a-4dc6-a12d-e02b9cad013e" />


Why this fix is needed:
----------------------
Signature fields are stored as binary, but they require the dedicated signature widget to render correctly.
By marking binary as a supported field type for the signature widget, Studio can
 properly detect and offer the widget during field configuration.
Given that this widget is very domain-specific and not intended for general binary fields, it was not added to
[web_studio/static/src/client_action/view_editor/editors/sidebar_safe_fields.js](https://github.com/odoo/enterprise/blob/17.0/web_studio/static/src/client_action/view_editor/editors/sidebar_safe_fields.js) though this may be reconsidered
after this fix the option is accessible only when the debugger mode is on, if want to show this widget 
to all the binary type fields even when the debugger mode is off the we'll have to add it to this file.

OPW : 5260188


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#237287