Steps to reproduce:

- Open the website editor.
- Add a carousel snippet to a page.
- Remove content from the first slide so it is shorter.
- Save the carousel as a custom snippet.
- Open the snippet dialog and locate the custom snippet. => The preview height is too small.

Before this commit, the preview height was computed from the scaled size, so shorter slides made the preview min-height too low.

After this commit, the preview height uses the layout size so the min-height stays consistent with other slides.

----------

Steps to reproduce:
- Open the website editor.
- Open the snippet dialog and resize the window.
=> The parallax preview background shifts to the left.
- Save a snippet with a parallax zoom in/out effect as a custom snippet.
- Open the snippet dialog and locate the custom snippet.
=> The preview shows a top to bottom effect instead of zoom.

Before this commit, resizing the snippet dialog could offset the
parallax background to the left, and zoom previews looked like top to
bottom effects.

After this commit, the preview keeps the background aligned and shows
zoom in/out effects for custom snippets.

Fixed parallax is still not previewed because it would require an
oversized background in the dialog.

----------

Steps to reproduce:

- Open the website editor.
- Save a "Carousel" snippet as a custom snippet.
- Open the snippet dialog.
=> The custom snippet shows no label.

Before this commit, custom previews dropped the base label so the dialog
showed no tag for custom snippets.

After this commit, custom previews reuse the base label.

task-5156137

**To see/test the bug, the change made in https://github.com/odoo/odoo/pull/244251 must be present**

Currently, users can `create` new `Lots/Serial Numbers` directly from the 
Contacts app via the `Lots/Serial Numbers` smart button.

**Steps to reproduce:**
- Install the `stock` and `contacts` modules.
- Enable `Lots & Serial Numbers` from the inventory settings.
- Open the `Contacts` app and open any contact record.
- Click the `Lots/Serial Numbers` smart button.

**Observation:**
The user can `create` a new lot/serial number from the Contacts, even 
though this flow is not supported and results in inconsistent data.

**Root cause:**
After PR [1], `lot/serial number` creation was accidentally enabled from the 
Contact. The intended behavior is that Contacts should only be able to view 
related lots/serial numbers, not create them. (Confirm with PO `crl`)

**Fix:**
This commit disables the creation of Lot/Serial Numbers from the contact by 
`hiding` the New button. This prevents users from creating inconsistent records 
until a complete and correct flow is implemented in a future improvement 
as mentioned at [2].

[1]:
https://github.com/odoo/odoo/pull/184242

[2]:
https://www.odoo.com/mail/message/978482657

opw-5504073

Currently, an `incorrect warning` message is shown when sending an invoice to 
`DIAN` or `Carvajal`, if the invoice date is 6 days before today, even though this 
date should be considered valid.

**Steps to reproduce:**
- Install the `l10n_co_dian` module and switch to the `CO company`.
- Go to `Invoicing` and create a new invoice with `taxes`.
- Set the `Invoice Date` to 6 days before today.
- Click `Confirm` > `Send`, ensure `DIAN` is selected, and `send` the invoice.
- Observe the warning message.

**Observation:**
`The issue date can not be older than 5 days or more than 5 days in the future.`

**Root cause:**
At [1] and [2], the allowed invoice date range is incorrectly computed, using 
`5 days in the past` and `10 days in the future`. This does not match the Colombian 
regulations and triggers incorrect validation errors for valid invoice dates.

These checks are intentionally implemented in both modules because they apply
at different stages and for different providers:
1) `l10n_co_dian`
When `DIAN: Free service` is selected as the `Electronic Invoicing Provider`
from the `Invoicing Settings`, the date constraint is evaluated at `send time`.
After the invoice is created, the validation is performed when the user sends 
the invoice to `DIAN`, and a blocking error is raised as a `UserError` if the 
invoice date is outside the allowed range.

2) `l10n_co_edi`
When `Carvajal` is selected as the `Electronic Invoicing Provider`, the same 
rule is checked `at the confirmation time` of the draft invoice. In this case, 
the validation results in a `chatter message`, not a blocking send-time error.

**Fix:**
This commit updates the date constraint logic to allow invoices dated up to 
`6 days before and 6 days after` the current date, in accordance with the 
DIAN specification described in Anexo Técnico – Documento Soporte No Obligados, 
page 59, at [3].

<img width="1089" height="120" alt="DIAN" src="https://github.com/user-attachments/assets/408c5ccc-5fed-4585-a81e-dce4ccb98b40" />

[1]:
https://github.com/odoo/enterprise/blob/2217827c0989fc5fc8d52a6a9b6f6c6d00b9773f/l10n_co_dian/models/account_edi_xml_ubl_dian.py#L672-L679

[2]:
https://github.com/odoo/enterprise/blob/913e55abc4a9aa58509aa2a60d378fb552de554d/l10n_co_edi/models/account_edi_format.py#L574-L603

[3]:
https://www.dian.gov.co/impuestos/factura-electronica/Documents/Anexo-Tecnico-Documento-Soporte-No-Obligados.pdf

opw-5482555

Forward-Port-Of: odoo/enterprise#107255
Forward-Port-Of: odoo/enterprise#105763

# Steps to reproduce
- Open Timesheets
- Go to list view
- Refresh page
- Total is formatted as regular float instead of time

# Cause of the issue
The list view uses the `timesheet_uom_timer` widget for the `unit_amount` field. While the row entries were formatted correctly since the widget is added to the fields registry in `timesheet_uom_timer.js`, the aggregate (total sum) is not formatted in the same way because the formatters registry is missing that particular widget.

Switching to the grid view and going back to the list view would solve the formatting. That is because the `timesheet_uom_timer` widget is added to the formatters registry when loading the grid view (in `timesheet_grid_uom_service.js`).

We ensure the formatter is registered globally by patching the `timesheetGridUOMService` outside the grid view context, ensuring consistent aggregate formatting in list view, even after a page refresh.

task-5907954

Forward-Port-Of: odoo/enterprise#107203
Forward-Port-Of: odoo/enterprise#107006

Currently, an error occurs when user edits a reconciled line.

**Steps to Reproduce([Video](https://drive.google.com/file/d/18dSAsZCl---wfCkMBfyo9LviTqgq3qpK/view)):**

 - Install the `Accounting` module.
 - Create an `invoice` with an `invoice line` having an amount greater than zero.
 - `Confirm` the invoice.
 - Go to the `Bank journal` and create a `statement line` with the same amount as the invoice.
 - Click `Reconcile` on that `statement line` and select the newly `created invoice line`.
 - Click the `pencil icon` to edit the line, enter a `positive amount` in the Balance field, and save.

`UnboundLocalError: local variable 'original_base_lines' referenced before assignment`

The error occurs because, when a specific condition [1] becomes true, the variables original_base_lines and original_tax_lines are expected to be defined. However, if reconciled_lines_ids is present in move_line_to_edit, these variables are never initialized and are later referenced, causing the UnboundLocalError [2].

This commit ensures that original_base_lines and original_tax_lines are initialized to None, which prevents the error.

[1]- https://github.com/odoo/enterprise/blob/fa4bbc20f25ec12c609ebbf37885e48900619de5/account_accountant/models/account_bank_statement.py#L1393-L1394

[2]- https://github.com/odoo/enterprise/blob/fa4bbc20f25ec12c609ebbf37885e48900619de5/account_accountant/models/account_bank_statement.py#L1410-L1411

sentry-7189027839