Add top KPI cards and replace the sales/purchase journal graph with a
monthly paid/unpaid stacked bar chart, this new graph is based on posted
invoices and bills over the last 13 months.

Add a debug-only journal option to disable sales/purchase dashboard
charts as it's useful for large DBs where chart computation can slow
down the dashboard rendering.

Remove the last statement line from the bank journal card as it's
redundant, the user can see this either by going to the statement list
or in their transaction.

---
Add an invoice layout configuration card to the kpis banner in the
accounting dashboard as long as the layout is not configured.

Also loosen the access rights and allow the normal account users to set
this configuration themselves so now it's not just admins.

---
When sending an invoice without a configured document layout, the layout
configuration wizard currently blocks the send flow if the user discards
it.

Replace the discard action in this invoice-specific flow with a
configure later action. This continues the original send flow using the
default layout, while keeping the layout unconfigured.

task-[6319113](https://www.odoo.com/odoo/project/967/tasks/6319113)

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

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/a73559ee4f [REL] 19.5.0-alpha.13 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/bb965c63da [FIX] icons: align data filter icon with material icon [Task: 6276321](https://www.odoo.com/odoo/2328/tasks/6276321)
https://github.com/odoo/o-spreadsheet/commit/8900dbec98 [IMP] icons: replace script as cjs instead of python [Task: 6276321](https://www.odoo.com/odoo/2328/tasks/6276321)
https://github.com/odoo/o-spreadsheet/commit/a5ef0a0405 [FIX] css: fix issues with the new material design [Task: 6475791](https://www.odoo.com/odoo/2328/tasks/6475791)
https://github.com/odoo/o-spreadsheet/commit/08b1a1d180 [FIX] standalone_viewport: stop following selection [Task: 6481678](https://www.odoo.com/odoo/2328/tasks/6481678)
https://github.com/odoo/o-spreadsheet/commit/f66629eea7 [IMP] charts: scorecard now uses formula instead of cell reference [Task: 6343843](https://www.odoo.com/odoo/2328/tasks/6343843)
https://github.com/odoo/o-spreadsheet/commit/b289465e09 [IMP] menu_registry: ensure children unicity [Task: 5224033](https://www.odoo.com/odoo/2328/tasks/5224033)
https://github.com/odoo/o-spreadsheet/commit/9358c3ddc8 [FIX] inputs: explicitly define border-style [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)

Co-authored-by: Florian Damhaut (flda) <flda@odoo.com>
Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com>
Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com>
Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Ronak Mukeshbhai Bharadiya (rmbh) <rmbh@odoo.com>
Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Rémi Rahir (rar) <rar@odoo.com>
Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com>
Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
Co-authored-by: Marceline Thomas (matho) <matho@odoo.com>

`BaseModel.load()` resolves every `field:id` column through `ir.model.data` one row at a time, behind a fixed 1024-entry LRU. A data file that references more distinct external ids than the cache holds, and reuses them across rows, overflows it immediately, so almost every row misses and costs a query.

`l10n_us/data/res.city.csv` is the only file in the codebase that does both: 31,236 rows over 3,172 counties. Installing the module costs 14,610 queries. Raising the cache to 10000 brings that to 3,859 with no change to the data loaded. Module load time is unchanged, the gain is in database round trips.

An entry is an external id mapped to a (model, id) tuple, and the LRU keeps a second dict to track ordering, so about 190 bytes each. The cache is built per `load()` call and dropped when it returns, and it fills to the number of distinct external ids in the file rather than to its cap:

| entries | case | bytes | MB |
|---|---|---|---|
| 1,024 | today's cap | 207,248 | 0.2 |
| 3,223 | res.city.csv working set | 640,240 | 0.6 |
| 10,000 | cap reached | 1,878,288 | 1.9 |

No data file in either repo reaches the cap.

task-none

Some generic validation errors raised by core account models lack enough context to identify which record caused the issue, making FEC imports harder to troubleshoot.

This commit improves the two error cases identified for this use case:
- `account.account._check_account_code` now includes the invalid account code in the error message.
- `account.move.write` now includes the move name/reference and displays human-readable field labels instead of technical field names when attempting to modify read-only fields on posted entries.

Although motivated by FEC import, these are generic core validations, so the improvements are implemented at the source to benefit all callers rather than only the FEC import flow.

Enrichment is scoped to the two cases above, other constraints/errors across these models are intentionally left unchanged for now, since editing core error messages more broadly should be done deliberately and on a case-by-case basis, not as a blanket rewrite

task-5346068

Forward-Port-Of: odoo/odoo#283279
Forward-Port-Of: odoo/odoo#281746

## Purpose

This PR revises the VoIP call flow editor and the configuration of its related resources based on FP's review.

The objective is to make call flows easier to build, move routing and scheduling concerns to the appropriate level, and provide more focused interfaces for selecting, creating, and configuring records.

## Call flow editor

- Allow nodes to be added by clicking an item in the sidebar, in addition to drag and drop.
- When possible, automatically connect a node added by click to the latest available output.
- Simplify the `Start` node:
  - display it as a green circular phone entry point;
  - keep a single output;
  - remove phone number and schedule configuration from it.
- Display `Hang Up` as a red circular endpoint with a hang-up icon.
- Manage the association between phone numbers and call flows from the Phone Numbers list view.
- Add explicit failure outputs to nodes where a failed call requires a separate destination.
- Improve the visual hierarchy of call group and queue nodes:
  - display the selected record name as the primary information;
  - display members or agents using muted secondary text.
- Refresh record-backed nodes after their configuration is edited.

## Record selection

For every node backed by an Odoo record:

- open the search dialog directly instead of opening an intermediate form containing a many2one field;
- apply the selected record directly to the node;
- keep record creation available from the search dialog;
- keep unconfigured record nodes out of the graph when creation is cancelled.

This applies to audio messages, contacts, users, call groups, queues, IVRs, extensions, and voicemail boxes.

## Time conditions

Replace inline schedule configuration with standalone `Time Condition` records managed directly from call flows.

A time condition contains:

- a timezone;
- one or more Open or Closed periods;
- period selectors for weekdays, days of the month, months, and optional hour ranges.

The node exposes two explicit outputs:

- `Open` for calls matching an open period;
- `Closed` for calls outside open periods or matching an exceptional closed period.

A warning indicates when no open period is configured, as calls will then always follow the Closed branch.

Time Conditions can be searched, created, duplicated, and reused from the call flow editor. Multiple conditions and orphan conditions are supported.

Depending on their position in the graph:

- a condition placed after Start controls the incoming call routing;
- a condition targeting a Call Group or Queue attaches its PBX schedule to that resource.

Schedule controls are consequently removed from Start, Call Groups, and Queues.

## Audio messages

Replace the generic audio-message form with a focused interface supporting:

- uploading or dropping a WAV file;
- recording audio;
- generating speech from text with a selected language and voice;
- previewing the resulting audio before saving.

Uploading or recording selects the uploaded-audio source and clears the text-to-speech content. Entering text selects the TTS source.

Generating TTS from a creation dialog keeps the dialog open and reloads the generated audio in place. Sounds created from a call flow are correctly applied to their node instead of closing the dialog or leaving an invalid node in the graph.

## Call groups

Simplify the call group form:

- remove the description;
- keep the group name, extension, and users prominent;
- move the extension to the right side and hide it in the call flow context;
- set the default timeout to 10 seconds;
- clarify that a zero timeout disables it;
- remove the user-specific timeout;
- remove schedule configuration.

## Queues

Simplify and reorganize the queue form:

- remove the description;
- move queue options into the main form;
- keep Allowed Agents as the only tab;
- reorganize the fields into two columns;
- place connection codes after the allowed users;
- move extension and music-on-hold settings to the right column;
- hide the extension in the call flow context;
- display timeout units explicitly;
- remove schedule configuration.

## IVR menus

Simplify the menu form and terminology:

- remove the description;
- keep inputs as the primary configuration;
- regroup secondary settings under an Options tab;
- clarify greeting, invalid-input, timeout, and abort behavior;
- hide standalone destinations when configuring the IVR from a call flow.

Menus now delegate to their Menu Sound:

- the Menu name is also used as the Sound name;
- upload, recording, TTS generation, and audio preview are embedded directly in the Menu form;
- generated audio is reloaded without closing the Menu dialog;
- PBX synchronization is deferred until call flow configuration is complete.

## Voicemail boxes

Simplify the voicemail form:

- place the user, greeting sound, and notification email in the left column;
- place the mailbox number in the right column;
- clarify the email label and provide field examples;
- replace the embedded message list with a stat button opening the dedicated message view.

## Call forwarding

Simplify user call-forwarding preferences:

- replace the separate always-forward option with no-answer and busy forwarding rules;
- use a zero-second no-answer timeout for unconditional forwarding;
- allow forwarding to an internal resource, dialable extension, or external number;
- default no-answer forwarding to the user's phone after 3 seconds, or to their personal voicemail after 20 seconds when no phone is configured;
- keep busy-call forwarding disabled by default.

## Testing

Tests are added or updated alongside each change, with coverage for:

- call flow interactions and automatic connections;
- record selection, creation, cancellation, and refresh behavior;
- Time Condition periods, routing, and PBX synchronization;
- audio upload, recording, TTS generation, and preview;
- IVR delegated sounds and deferred synchronization;
- Start and Hang Up node rendering and behavior.

task-6472451