B2G invoices are not sent via Peppol but to Chorus Pro (via the
approved platform).
Chorus Pro is the platform with ID 9999 on the annuaire.
Any invoice to partner associated with that platform on the annuaire
is considered B2G (business to government).

From a user point of view nothing much changes, except that they have
to set some additional fields for which we rely on the existing module
`l10n_fr_facturx_chorus_pro`.

From a technical PoV we store the information whether a partner is
behind Chorus Pro in the `peppol_supported_documents` field.
(By putting the special document identifier for Chorus Pro invoices there.)
We retrieve the information whether a partner is behind Chorus Pro / B2G
from the annuaire lookup.


The following new lifecycle statuses have been added. They are
required for the functional tests for the Chorus Pro connection.
- Sent (sent by the platform)
- Suspended
- Completed (to "resume" the "Suspended" state)

See the related IAP PR: https://github.com/odoo/iap-apps/pull/1804

task-6278159

Forward-Port-Of: odoo/odoo#284677

This commit adds an index on `(journal_id, date)` to speed up `_get_last_sequence_domain`.

The slow part is

`.search(domain, order='date [desc|asc]', limit=1)`

Because of the order by date, postgresql scans the index on `date`, assuming a row will be quickly matched.

If this assumption is wrong though, it'll scan a large part of the index or all of it, which is slow.
This is the case with account move 17102258 on odoo.com at the time of writing this.

- before
   - 1st query https://explain.dalibo.com/plan/6b8ff62b1572ah1a
   - 2nd query https://explain.dalibo.com/plan/41243cgccg5798gb
- after
  - 1st query https://explain.dalibo.com/plan/4fd2c7ed28g7b138
  - 2nd query https://explain.dalibo.com/plan/2heh6c6965c88h71
  - ~~1st query https://explain.dalibo.com/plan/f874a31f4b07hdeb~~
  - ~~2nd query https://explain.dalibo.com/plan/e8h09725gfh4c2e9~~

full `web_read`
- before ~1min 10s
- after ~650ms

task-6481393



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

Forward-Port-Of: odoo/odoo#283159

[IMP] website: merge countdown snippet layout and template options

Following [commit](https://github.com//odoo/odoo/commit/74a9e5bb734708497456ed2bc91465f95505b2d7), we'd like to improve the countdown snippet.
Key changes:

1. Merge Layout and Template into a single layout option with the following layouts:
   - Circle
   - Text Inline
   - Dominoes (replaces Boxes)
   - Wrapped Numbers
   - Text
   - Big Numbers (replaces Clean)
2. Enable toolbar for both metrics and indicators
3. Remove Edge Spacing
4. Convert Circle layout to Text Inline format: display the countdown
on the left with reduced size.
6. Retain Circle-specific options plus all Text Inline options when
possible.

task-5242156

---

[IMP] website, html_builder: show notification if countdown is outdated

We would like to show the notification to user saying that the
countdown is outdated if it should be updated.
This commit also changes wording in that notification to indicate that
it may cause problems.

task-5242156

---

[IMP] website, html_editor: add countdown toolbar namespace

For metrics in countdown, we don't want to show all toolbar groups, but
rather just font and decoration groups buttons. This commit adds a new
namespace for that, and adds that namespace to buttons we want to
display.

task-5242156

Feedback from the Dimona UX review:

- The Dimona badge on the employee form sat before the review state pill and was a dropdown, so the state could be set by hand. That state reflects what was declared to the ONSS, not a user choice: it becomes a read-only badge, placed after the review pill, and "Send Dimona" stays the only way to act on it. dropdown_selection_badge honors a readonly attribute on the field node for this; props.readonly could not be used, as list and kanban records are never in edition, which would freeze the review state badge as well.

- The manual declaration wizard always showed "Dimona IN" with the text of an entrance declaration, whatever had to be declared. Its title and description now follow the next action (in, out, update, cancel or issue), and the ONSS link points to the Dimona portal instead of the DmfA instructions.

- The ONSS certificate setting only said "Configure ONSS certificate". It now states what the certificate is for, automating Dimona, DMFA and DRS submissions via the API, and links to the ONSS page explaining how to obtain the credentials.

- The Dimona declaration fields on the employee offered to create a declaration from the autocomplete, which would record a declaration that was never sent to the ONSS.

task-6470879

Commit odoo/odoo@1facbc0646bd made the checkout validate every `website.checkout.step` through a single flow, but the localization invoicing steps were left out.

These steps are shown or hidden by publishing or unpublishing a shared step record on each checkout. This is unreliable: the cart and payment pages don't refresh it, so the step can be left in the state set by another visitor. The step is also only validated when the visitor goes through it, so opening `/shop/payment` directly skips it. An override also forces `try_skip_step` off so the checkout page cannot jump past the step.

This commit filters the Chilean and Mexican step out of the breadcrumb steps domain per request when it is not needed, instead of toggling the shared record, and checks it in the validation flow so opening `/shop/payment` redirects back to it while incomplete. Forcing `try_skip_step` off is no longer needed. Chile stores the taxpayer type on the invoicing customer so the check also works when the billing contact is not the ordering one. Mexico uses a best-effort check, since a customer who wants no invoice looks the same as one who skipped it.

task-6045788

See also:
- https://github.com/odoo/odoo/pull/276844
- https://github.com/odoo/upgrade/pull/10806