Before this commit, the action service added a `params` key into
the context, typically when doing a `loadState`, i.e. loading the
state from the url. The value of that key was the state of url (an
object with, amongs other things, a `actionStack` key,
representing the current breadcrumbs, a typical JS thing).

Adding this key was a mistake from day 1, as it was then sent to
the python at each rpc. It means that the context sent to load a
form view was different before and after a page reload, which
doesn't make sense. Worse, it caused an issue with the newly
introduced cache system [1], as we did a cache miss on reload, due
to that altered context. To circumvent that, we manually removed
that key in RelationalModel, before loading data.

However, this caused an issue in website, as the code was actually
using that `params` key mecanism: they relied on the fact that it
was automatically added by the framework in some cases (F5), and
built it themselves in other case (calls to doAction).

This commit properly fixes the issue we tried to fix in [1]: we no
longer add the `params` key when loading the state from the url.
So we don't need to remove it later anymore. We obviously had to
adapt a bit the code in website. We added some props to parameterize
the WebsideBuilder action, and that component now also reads
directly into the state of the router. We also introduced an
`extractProps` mecanism (like we have for fields), to convert an
action (especially its `params`) into props to provide to the
client action itself.

[1] https://www.odoo.com/odoo/project/133/tasks/4479845

task-4901018

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/5cecc0ed4 [REL] 18.4.1 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/80608aa25 [FIX] animations: fix pivot collapse animation [Task: 4894210](https://www.odoo.com/odoo/2328/tasks/4894210)
https://github.com/odoo/o-spreadsheet/commit/3c8fb24ef [FIX] composer: zone selection with arrow keys [Task: 4890605](https://www.odoo.com/odoo/2328/tasks/4890605)
https://github.com/odoo/o-spreadsheet/commit/a750a4062 [FIX] Selection: Fix navigation through merges [Task: 4873718](https://www.odoo.com/odoo/2328/tasks/4873718)
https://github.com/odoo/o-spreadsheet/commit/f09ac3bed [FIX] CFSidePanel: do not crash when deleting the edited CF [Task: 4880418](https://www.odoo.com/odoo/2328/tasks/4880418)
https://github.com/odoo/o-spreadsheet/commit/a5b7cad60 [REL] 18.4.0 [](https://www.odoo.com/odoo/2328/tasks/)
https://github.com/odoo/o-spreadsheet/commit/7389b696e [IMP] clickable cell: add tooltips on links [Task: 4551511](https://www.odoo.com/odoo/2328/tasks/4551511)
https://github.com/odoo/o-spreadsheet/commit/3e938c19a [FIX] SidePanel: Export interface to resolve types [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)

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: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com>
Co-authored-by: Florian Damhaut (flda) <flda@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>

**Problem:**
When having products that were sold with Intrastat (which permits
the selling of products accross borders in the EU), the weight was
not correctly displayed. The weight always had the '.' decimal
separator, regardless of the language. In French, the decimal
separator is ',' but a product weighting 3 and a half kilos would
be displayed 3.5 instead of 3,5. The same can be said about the
supplementary unit column.

**Steps to reproduce:**
- Change your company to belong to the EU.
- Change the langugage to one that takes a comma as a decimal separator, like French or Spanish.
- Create a product that has a weight in the inventory tab, as well as intrastat values in the accounting tab.
- Make a sale for this product with a client in another country belonging to Intrastat and confirm the invoice.
- Go to Instrastat report in accounting in the audit reports.
- The weight is not correctly displayed.

**Cause of the issue:**
The language of the user was not taken into account when
fetching the data.

**Fix:**
The fields are now changed depending on the current language,
to match the needed decimal separator.

opw-4575332

**Problem:**
the split of the landed cost between lots doesn't
take into account if a lot has no quantity left
or if it has less than it's initial quantity

**Steps to reproduce:**
- enable the "lot & Serial Numbers" and "landed costs" settings
- create a storable product, tracked by lot
- in general information activate "valuation by Lot/Serial Number"
- select FIFO as the category
- create a request for quotation for this product for a quantity of 5 and a unit price of 10.000
- confirm and click on the receipt smart button
- on the move line click on the Lots/serial number widget on the right
- create 4 lots (L1 with 1 units, L2 with 2 units, L3 and L4 with 1)
- save and validate the picking
- create a sale order for a quantity of 2 of this product, confirm it and validate the picking
- create a new service product, in "purchase" check "is a landed cost"
- open accounting/vendors/bills, create a new one for the same vendor as the purhase order
- add a line with the landed cost and a price of 5000 (quantity of 1)
- set a bill date and save
- clik on "create landed costs"
- in the "transfers" field write the refernce of the receipt of the PO
- open inventory/reporting/valuation and type your product in the search bar

**Current behavior:**
4 lines were created :
a line of 600 for L1
a line of 1200 for L2
a line of 600 for L3
a line of 600 for L4

an additional issue, is that if we now sell the 3 remaining quantity and search our product in inventory/reporting/valuation the quantity will be zero but total value will be 600

**Expected behavior:**
the spliting should adapt to the remaining quantities like it does when lots are not involved
(for instance when there is a landed cost linked to a PO with a quantity of 5 but only 4 of those products are still in stock the value of the landed cost valuation line linked to this product is 4/5 of the landed cost)

So here it should be :
no line for L1 (no remaining quantity in L1)
a line of 1000 for L2 (only 1 remaining, so a third of the 3000 (3/5 * 5000)) a line of 1000 for L3
a line of 1000 for l4

**Cause of the issue:**
the quantity used is the one of the initial stock move line so it doesn't take into account the current number of product in the lot

opw-4828963

reproduction:
18.0+18.1:
1. In Todo, insert an inline image, and create a link including the image and some text
2. click on the text part, click edit button, modify the label area and click apply
3. the image is removed

Test case 2:
1. go to Recruitment, and open an application and click "Send interview"
2. click on the link inside the template, change the url
3. apply, format of the button breaks

18.2:
same flow with test case 2, click apply causing a traceback

18.3:
same flow with test case 2, click on the link, do nothing and click away, the popover not close

Fix: a partial back port of https://github.com/odoo-dev/odoo/pull/4633 The idea is that when the link doesn't only contain text, we don't show the label input field nor apply the label to the link. Because the label field extracts/display the text content of the link element, the field doesn't support html fragment, applying the label on a link including another element inside will break it.

task-4881878

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

**Steps to reproduce the issue:**
- Install Stock, Sales applications
- Set the allowed companies to Marc Demo to be only one company
- Change the user to Marc Demo
- Create a SO with partner another company than Marc's company
- Confirm the SO

**Issue:**
A traceback is raised:
`No rule has been found to replenish "product" in "Virtual Locations/ Inter-company transit". Verify the routes configuration on the product.`

**Root Cause:**
- When the procurement group searches for a pull rule with a destination location set to the inter-company transit location (due to the partner's company being different), the rules for the inter-company transit location are not automatically applied.
- The `_get_rule_domain` method https://github.com/odoo/odoo/blob/05cff3b7d866f6bc95c4b32f343ae14a4da946f2/addons/stock/models/stock_rule.py#L641-L653 modifies the destination location to the customer's location if:
  - The user belongs to the `base.group_multi_company` group.
  - The destination location is the inter-company transit location.
- In this use case, the user does not belong to the `base.group_multi_company` group because they are restricted to a single allowed company.

Additionally, the logic in `_compute_location_dest_id` https://github.com/odoo/odoo/blob/05cff3b7d866f6bc95c4b32f343ae14a4da946f2/addons/stock/models/stock_move.py#L227-L231 for inter-company transfers does not account for users with a single allowed company.

**opw-4749870**

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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