[FIX] CorePlugins: Prevent dispatch during adaptRange

[fw-bot]

The method adaptRange was originally designed for each plugin to update their own ranges, whithout having to manually react to the different commands that alter the sheets structure.

We have abused the system when we introduced the spreadsheet pivots to allow the modification of a pivot dataset (which is stored in PivotCorePlugin) from another entry point SpreadsheetPivotCorePlugin) by dispatching an UPDATE_PIVOT command but there are some side effects that we did not account for, the dispatched command is forwarded to EVERY other plugin. Meaning that during an adaptRange, which should only concern a specific plugin, we end up notifying a change to the whole core/coreview stack.

This revision removes the access to 'dispatch' during the handling of adaptRange so we ensure that the changes are kept locally.

Task: 5380747

Description:

description of this task, what is implemented and why it is implemented that way.

Task: TASK_ID

review checklist

• feature is organized in plugin, or UI components
• support of duplicate sheet (deep copy)
• in model/core: ranges are Range object, and can be adapted (adaptRanges)
• in model/UI: ranges are strings (to show the user)
• undo-able commands (uses this.history.update)
• multiuser-able commands (has inverse commands and transformations where needed)
• new/updated/removed commands are documented
• exportable in excel
• translations (_t("qmsdf %s", abc))
• unit tested
• clean commented code
• track breaking changes
• doc is rebuild (npm run doc)
• status is correct in Odoo

Forward-Port-Of: #7630
Forward-Port-Of: #7603

[robodoo]

[fw-bot]

@rrahir @LucasLefevre cherrypicking of pull request #7603 failed.

stdout:

Auto-merging src/helpers/pivot/pivot_registry.ts
CONFLICT (content): Merge conflict in src/helpers/pivot/pivot_registry.ts
Auto-merging src/plugins/core/pivot.ts
Auto-merging tests/range_plugin.test.ts

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

⚠️ after resolving this conflict, you will need to merge it via @robodoo.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[rrahir]

robodoo r+