## Summary

- Vendors the canonical [ace-builds](https://github.com/ajaxorg/ace-builds) `mode-json.js` into the `web.ace_lib` bundle, so the Ace editor can syntax-highlight JSON content.
- Registers `"json"` in `CodeEditor.MODES` so `widget="ace" options="{'mode': 'json'}"` passes the prop validator.
- For readonly editors only, re-enables `showGutter` and `showFoldWidgets` when `mode === "json"` — this is what makes the fold triangles in the gutter clickable for users viewing read-only JSON (config snapshots, API response logs, audit fields, etc.). Other modes keep their existing behavior of hiding the gutter when readonly.

## Why

Odoo ships the Ace editor with modes for `js`, `xml`, `qweb`, `python`, and `scss`, but not `json`. Custom modules that surface JSON payloads (third-party API responses, structured logs, configuration blobs) have no native way to render them with syntax highlighting; today they either fall back to a plain `<field>` or vendor their own `mode-json.js`, which is fragile.

This is the smallest change that solves the gap consistently for everyone:
- The mode lives next to the other vendored ace modes.
- The `CodeEditor` API surface is unchanged (just one more allowed value for `props.mode`).
- The readonly gutter override is narrowly scoped — no behavior change for any other mode.


The vendored `mode-json.js` is the standard ace-builds file, adapted minimally to match the existing files in `addons/web/static/lib/ace/`:

## Test plan

- [ ] In a development DB, open a view that renders an ace JSON field — e.g.
  ```xml
  <field name="some_text_field" widget="ace" options="{'mode': 'json'}"/>
  ```
  and confirm: syntax colors are applied; brace matching highlights pairs; `Ctrl+/` line-comments; typing JSON behaves the same as in `python` / `js` modes.
- [ ] On the same field with `readonly="1"`, confirm the gutter is visible and fold triangles appear next to every `{` and `[`. Clicking a triangle collapses the block; clicking it again expands. Keyboard shortcuts (`F2`, `Alt+L` / `Cmd+Option+L`) also fold/unfold.

### Description of the issue/feature this PR addresses:
Prevent Out of Memory (OOM) crashes and drastically improve execution speed when generating the Swedish SIE4 verification export for massive datasets.

### Current behavior before PR:
When exporting a large volume of journal entries (e.g., 190,000+ account moves), the `_export_l10n_se_sie4_verification` method relies on iterating through heavy ORM recordsets and accessing relational child fields (move.line_ids) inside a loop. This triggers a severe N+1 query problem, maxing out server RAM and causing an OOM crash.

### Desired behavior after PR is merged:
The method now utilizes a hybrid data extraction approach:
- The ORM is used strictly to safely evaluate domains (multi-company rules, dates, states) and fetch a lightweight list of valid move_ids.
- A single SQL query with JOIN statements fetches all parent moves, child lines, and account codes in exactly one database query.
- itertools.groupby chunks the flat, lightweight dictionary results back into their respective journal entries.
The export now handles massive datasets in seconds with minimal memory overhead, while remaining perfectly secure.

### Benchmark:

For Memory:
| # Input Data | Before PR | After PR |
| -------- | -------- | -------- |
| ~190,000 moves | MemoryError | 407MB|
| ~200,000 moves | 1.8GB | 174.8 MB|

For Speed:
| # Input Data | Before PR | After PR |
| -------- | -------- | -------- |
| ~190,000 moves | MemoryError | 5.10s |
| ~200,000 moves | 1m29s| 5.3s|

### Reference:
opw-6067999

Steps to produce:
---
- Install website_sale module.
- Enable `Comparison Price` from settings.
- Create a product with sales price = 25 and compare price = 25.
- Go to the shop page and search for the product.

Issue:
---
- The strikethrough appears on the compare price (25) even when the compare price equals the sales price.
- The strikethrough should only appear when the compare price is strictly greater than the sales price.

Root cause:
---
- In `_search_render_results_prices` [1], the condition only checks for the presence of `compare_list_price` in `combination_info`, without verifying that it is actually greater than the sales price. This causes the strikethrough to render even when both prices are equal.

Solution:
---
- Added a strict greater-than check on compare price against the sales price, aligning with the existing behavior already implemented for the product page [2].

Before:
---
<img width="537" height="98" alt="image" src="https://github.com/user-attachments/assets/a1524f0f-4a59-4daf-ac7d-834604710492" />

After:
---
<img width="538" height="95" alt="image" src="https://github.com/user-attachments/assets/1e32269b-13c0-469b-9d1f-e6d6ced97fdd" />


[1]https://github.com/odoo/odoo/blob/4ca059731f97d0f9bce4863cf195fd68a755717e/addons/website_sale/models/product_template.py#L831-L834
[2]https://github.com/odoo/odoo/blob/4ca059731f97d0f9bce4863cf195fd68a755717e/addons/website_sale/views/templates.xml#L1340-L1346

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

Why this commit:
---

There are two instances in version 17.0 where dates use toLocaleString(), which relies on the device's local format instead of the Odoo-configured format.

Since Odoo already defines a standard date format, all toLocaleString() usages in pos should be replaced to ensure consistency.

Starting from version 17.0, cash in/out receipts and the sales report use the local device time format.

This commit updates those references and aligns them with the Odoo-configured date format. 
During forwardporting the fix in version 19.0 needs to be added to [base.js](https://github.com/odoo/odoo/blob/0352c5e8543b75083cf555c3d5b4f164f949b465/addons/point_of_sale/static/src/app/models/related_models/base.js#L64-L69).
As formatDateOrTime function is used in the [reciept header](https://github.com/odoo/odoo/blob/0352c5e8543b75083cf555c3d5b4f164f949b465/addons/point_of_sale/static/src/app/screens/receipt_screen/receipt/receipt_header/receipt_header.xml#L13) printing date on all reciepts. 

After this commit:
---

<img width="947" height="982" alt="image" src="https://github.com/user-attachments/assets/2d9e4199-75dd-40ea-aeb1-27401c9022f3" />


All date references consistently use the Odoo-configured date format.

OPW: 6087341





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