Description of the issue/feature this PR addresses:
When doing online payment in POS, customer may take some time and the POS may go to idle state. This causes when it goes to idle and back to alive, it will direct to the first screen.
Steps to reproduce:
- Create POS & setup POS online payment (use Demo online payment)
- Open POS, add a product, go to payment screen, select the online payment method
- Let it go to idle state (triggered by useIdleTimer)
- Move the cursor, or at least make it back to active state
- You'll see the screen be redirected to first screen
- Do the payment, it will redirect to TicketScreen with empty order info, and when you click new order the previous one is still hanging there

Alternatively take a look at the recording:
https://github.com/user-attachments/assets/b8e8ae81-df04-41e0-b122-002413714735

Current behavior before PR:
- Because it bounces to first screen, when attempting payment the pos does not have the order state 

Desired behavior after PR is merged:
- Do not redirect if in payment screen, so that order context won't be lost

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

This error occurs when `o.tax_totals` returns `False`, causing an AttributeError when accessed in the QWeb template.

Steps to Reproduce :

- Install the module `accountant.`
- Go to Reporting and open Tax Return.
- Open Closing Entry and Print.

`AttributeError: 'bool' object has no attribute 'get'`

The error occurs when printing the tax report for the first time. The system first attempts to display the document configuration popup for the user based on the account move. However, since `o.tax_totals is not available` in the tax report 
`(as it is a journal entry)`, and when the user`Configure Document Layout`, it raises a validation error.

At [1] we cannot print pdf when `move_type == entry` so it is better to hide `Print` button in this condition.

This error is resolved by hiding the `Print` button in the `Tax Return` `Journal Entries`, as it only contains journal items.

Link [1] : 

https://github.com/odoo/odoo/blob/63fc0d1cefaf8f59acd0743a225d1002425ff156/addons/account/models/ir_actions_report.py#L72

sentry-6115648026

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

Issue Before This Commit:
============================

When attempting to add a new valuation for a lot/serial-tracked product using the 'Add Manual Valuation' button while the 'Group By Lot' filter is applied, a 'ZeroDivisionError: float division by zero' traceback occurs.

Steps to Reproduce:
============================

- Install the stock_account module.
- Create a product, enable Lot/Serial tracking, and assign it to the Furniture category.
- Update the quantity and assign a lot/serial number, which creates a valuation layer for this lot-tracked product.
- Disable Valuation by Lot/Serial Number for the product.
- Go to Valuation, apply the Group By Lot filter, and try to create a new valuation by clicking Add Manual Valuation.
- Click on the Revalue button it will give an Error.

With This Commit:
============================

The issue occurs because when revaluing layers using the 'Add Manual Valuation' button, all layers have 0 remaining quantity. This happens if 'Valuation by Lot/Serial Number' was initially enabled, creating valuation layers for lot/serial-tracked products, and later disabled. As a result, all valuation layers associated with lot/serial numbers have zero remaining quantity. When attempting to revalue these layers while using the 'Group By Lot' filter, the error occurs.

This commit ensures that if all layers have 0 remaining quantity, a validation error is raised to prevent the issue.

task - [4668497](https://www.odoo.com/odoo/my-tasks/4668497)

### Steps to reproduce:
- Create a new DB on odoo.com/trial with Argentinean localization, and your Odoo email.
- After installation, a validation is raised: "Invalid length for CUIT".

### Here is what happens:
1. When creating a new company, the enrich function tries to complete data. 
If you created the database with an `odoo.com` email for example, the Company will be filled with a Belgian VAT.
https://github.com/odoo/odoo/blob/5bb57a916d3069cd609e07d401dd3b4c39f85954/addons/partner_autocomplete/models/res_company.py#L23-L28

2. The l10n_ar is then installed, and the CUIT will be set as the default identification. https://github.com/odoo/odoo/blob/9a44bc80a5f8bd1cfcb05a3a9f4abdbd67228488/addons/l10n_ar/models/account_chart_template.py#L37

3. Finally, the validation is triggered by the modification above. Obviously the Belgian VAT is not compatible with the CUIT format, which leads to a User Error.
https://github.com/odoo/odoo/blob/4c1d2025118b98e89c131a32d46015d9c6a3b032/addons/l10n_ar/models/res_partner.py#L56-L57

Note: to reproduce in local, you have to add IAP credits.

### Solution:
Solution:
When installing the l10n_ar package, let's only set CUIT as a default if the validation passes.

opw-4609583

## [FIX] web_gantt: make sure orm service is defined in gantt renderer

Before this commit, when the user reschedules his task with dependencies by clicking on any arrow displayed in the gantt connector. 
A notification is displayed to notify the user the action is done with success, that notification also contains an `Undo` button to 
let the user to undo the rescheduling made. However, if the user clicks on the undo button, a traceback occurs. The reason is because 
`orm` service is not defined in the gantt renderer.

This commit makes sure the orm service is defined in the gantt renderer to be able to call the `action_rollback_scheduling` method.

## [FIX] web_gantt: don't display undo button if old vals are not given

Before this commit, after the `web_gantt_schedule` call was done, a
notification is displayed according to the result received by the
`web_gantt_schedule` call done. The problem is even if the
`old_vals_per_pill_id` is not given when the gantt scheduling has been
made with success, the `Undo` button is displayed. The problem is
without `old_vals_per_pill_id`, it is impossible to undo the action
done, because the initial data before the `web_gantt_schedule` is not
known without that data, and so, if the user clicks on `Undo` button a
traceback will occur since we cannot retrieve the initial data of the
records processed in the `web_gantt_schedule` method.

This commit makes sure the `Undo` button is displayed only if we have
the information to `undo` the `web_gantt_schedule` method. To know that,
the `old_vals_per_pill_id` should be given in the result of
`web_gantt_schedule` to be able to revert the changes made by
`web_gantt_schedule`.

## [FIX] web_gantt: correctly display warning notification

Before this commit, a warning notification was not properly displayed
because the method does not return what we expect. Instead of returning
the message and notification type, it returns a client action to call
`display_notification`. Moreover, the warning notification does not
display the right icon, it display `fa-check` instead of `fa-warning`.

This commit changes the object returned for the warning to have the
expected values returned and changes the icon when the notification is a
warning one.

task-4687572

Currently, when settling customer's account using the mexican localization, the session crashes after selecting the payment method.

Steps to reproduce:
-------------------
* Install the mexican localization and switch to one of the company
* Create a new contact of type "Company"
* Create an invoice for that contact so that he has a due amount set
* Open session
* Select the customer and settle due amount
* Select any payment method
> Observation: Blank screen

Why the fix:
------------
Same issue addressed here but at a different place: https://github.com/odoo/enterprise/commit/e1e1abdd23cead2bcd7b8170da28161c3f5b2e15

Cause by the fact that when a customer of type "company" is selected we automatically invoice orders.
https://github.com/odoo/odoo/commit/270779c8250272920d759fbe7b6cfc889e2f5969

Instead of going in the same direction of the first fix, we never set `to_invoice` to true when we are settling customer accounts. It's pointless to set invoice to true when settling accounts as it's impossible to create an invoice without any product. This should also benefit localizations that invoice by default every order by bypassing the invoice in that case.

opw-4685842