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

The budget section of the project dashboard now displays budget types:

```
╔═══════════════════════╦══════════╦════════╦════════════╗
║                       ║ Forecast ║ Actual ║ Difference ║
╠═══════════════════════╩══════════╩════════╩════════════╣
║ Expense                                                ║
╠═══════════════════════╦══════════╦════════╦════════════╣
║ Office Setup          ║ $3,500   ║ $1,200 ║ $2,300     ║
╠═══════════════════════╬══════════╬════════╬════════════╣
║         Total Expense ║ $3,500   ║ $1,200 ║ $2,300     ║
╠═══════════════════════╩══════════╩════════╩════════════╣
║ Revenue                                                ║
╠═══════════════════════╦══════════╦════════╦════════════╣
║ Client Project Alpha  ║ $1,000   ║ $6,800 ║ $700       ║
╠═══════════════════════╬══════════╬════════╬════════════╣
║ Website Redesign      ║ $2,300   ║ $2,000 ║ $300       ║
╠═══════════════════════╬══════════╬════════╬════════════╣
║         Total Revenue ║ $2,400   ║ $8,800 ║ $1,000     ║
╠═══════════════════════╩══════════╩════════╩════════════╣
║ Both                                                   ║
╠═══════════════════════╦══════════╦════════╦════════════╣
║ Subscription Services ║ $2,200   ║ $1,900 ║ $300       ║
╠═══════════════════════╬══════════╬════════╬════════════╣
║            Total Both ║ $2,200   ║ $1,900 ║ $300       ║
╚═══════════════════════╩══════════╩════════╩════════════╝
```
The difference amount is also highlighted with an appropriate color based on its
budget type, improving clarity and usability.

task-4497632

*:appointment_account_payment

NEED
====

Before this change, users could not make a manual link between meetings
and a sale order, as is the case when booking a paid appointment. This means
that when in the back-end, the user can create a meeting for a paid appointment
but cannot link it to a SO(L).

SOLUTION
========

In order to centralize the management of appointments, in terms of quick
overview and creation, we want the user to still be able to create new
appointments from the gantt view, even in this use case. Therefore, we do
not implement a product configurator, like we did in Event for instance.

Instead, we simply give a visual feedback, being a top left triangle on
the gantt pill, when the meeting is linked to a paid appointment, but not
to any SO(L), meaning a payment may be due.

Then, on the form view of the calendar event, we add a button to create
a SO (when no SOL is linked, at least one partner beside the organizer
is set, and other conditions are met, see show_so_creation_button)

This button opens a new wizard, that allows some limited customization
before creating the SO: the user can choose between attendees (beside
the organizer's) and also toggle a confirmation of the SO on creation.
The appointment and the total reserved capacity are also reminded there.
Finally, the user can either create the SO or create and open it, in
order to inspect (and eventually modify) the created record.


Task-5012248

Before:
- The Labour Welfare Fund Summary report header only displayed the main title.
- Company information was missing, making reports less identifiable.
- Labour Identification Number was not included in the report output.
- Gratuity Calculation Report" was listed after "Labour Welfare Fund Report".
- Updated sequences so Gratuity appears before Labour Welfare.
- The LWF report displayed raw dates, resulting in inconsistent date formatting.
- The report wizard opened even when the active company was not Indian.
- LWF data was generated only from paid payslips, blocking use-cases where payslips were only validated.

After:
- Added company name below the report title for clearer identification.
- Displayed the Labour Identification Number in the header section.
- Updated sequences so Gratuity appears before Labour Welfare.
- Dates in the report header are now properly formatted as dd/mm/yyyy.
- The wizard checks the user’s active company and blocks access unless it belongs to India.
- LWF lines now include payslips in both validated and paid states, ensuring timely report generation

Impact:
- Enhances clarity and traceability of the LWF Summary report.
- Ensures users can easily identify which company and LIN the report belongs to.
- Provides accurate report output, prevents usage in non-IN companies, and aligns data generation with actual payroll workflow.

Task: 5000307

The link popover previously had multiple buttons, making the link
editing experience less intuitive. This commit unifies actions into
a single wider popover and refactors some logic to improve consistency.

## UI/UX changes:
- Replaced three buttons (copy, edit, remove) with one "Edit" button,
  which opens the link editing view.
   | Before  | After |
   | ------------- | ------------- |
   | ![image](https://github.com/user-attachments/assets/04727aea-fc7b-410b-9159-1ac56e9b42a0)  |  ![image](https://github.com/user-attachments/assets/512628c7-b425-4831-a90e-caa6b1868c3d)  |

- Widened the popover for better readability.
- Removed the copy link feature.

<br/>

## Changes in link editing view:
- Moved the "remove link" button in this view.
  <kbd>![image](https://github.com/user-attachments/assets/4ad69aa4-4edb-4a25-a7b0-f84e76cbcbce)</kbd>

- Updated URL input placeholder to: "Enter URL, /page, or #anchor".
- Auto-focus the URL input when creating a link for selected text.
- Auto-focus the label input when creating new links or editing
  existing links.

task-[4862671](https://www.odoo.com/odoo/project/974/tasks/4862671)

Co-authored-by: adch-odoo \<adch@odoo.com\>

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