This will allow both the OWL Option system and the Legacy system to work
alongside each other. Making it easier to convert step by step.

The original file will be the one used for the conversion. This will
allow any fix done in the master branch to hit the OWL file when rebased
since this is the file that will be kept at the end of the conversion.

task-3850413

[REF] website: split snippet options to legacy file

task-3850413

[REF] web_editor: convert UserValueWidget to ES6 class

The widget will be turned into a "state model" in future commits and
most of its code will be rewritten, but the first step is to turn it
into an ES6 class instead of a "Legacy" widget

task-3850413

This is the first step of a major refactoring to accommodate the current
SnippetsMenu stack to OWL. To do so, it split some of the logic, to
separate (as much as possible) state from UI HTML.

Previously, a lot of the widgets in the SnippetsMenu would rely on DOM
to handle their states and values. SnippetOption also had direct access
to the widgets and templates. This allowed Options to request values
from the child widgets and update their state accordingly.

The template for the option was also rendered using its own system.

Now, the SnippetOption is a simple ES6 class, and has no direct element
in the DOM. Instead, a SnippetOptionRendering component is passed to the
SnippetsMenu to render the "UserValueComponent" which is the UI the use
will interact with.

The state of these UserValueComponents are still handled by the
SnippetOption however. Which allows the SnippetOption to modify the
state of a component, and the component will re-render accordingly.

This means the XML rendering is no longer handled by the option and
widgets, but by OWL.

===== NOTE =====
This commit message is WIP but any suggestion is welcomed :D

task-3850413

[REF] web_editor: adapt visibility computation of UserValue to OWL

In this commit, some properties are renamed to better fit the new
framework. The `user_value_widget_request` trigger_up which was
previously a trigger_up is changed to a "callback".

The dependency system remains almost identical. Component just use the
state to apply d-none or not.

task-3850413

This follows the previous commit logic, with the added complexity of
handling the state of a toggler.

task-3850413

This commit adds WeButtonGroup which replaces the
ButtonGroupUserValueWidget

This commit SHOULD not reach master as this solution has not been
discussed and is IMO a big downgrade to the old tooltip system.

This commit changes the old SnippetOptionWidget class to an ES6 class
and adapts the template to OWL.

task-3850413

This commit combines we-datetimepicker and we-datepicker into one
Component with different props and converts the API to the new OWL api.

task-3850413

Co-authored-by: Arthur Detroux (ard) <[email protected]>

This commit convert we-row to owl and introduces the concept of layout
elements. Their state is also shared with the option so that it can
properly hide the layout elements when all of the layout's widgets are
hidden.

task-3850413

task-3850413

The templates are now static templates and the options are now ES6
classes. The layout mixin was also adapted so that it works with this
type of class.

This commit adapts the code so that it may work inside an OWL Component
while retaining most of its previous functionality.

task-3850413

This commit converts the API of the Mediapicker widget to OWL and
combines the Imagepicker and the Videopicker widgets into a common
WeMediapicker whose behavior depends on its props (specifically
`mediaType`, being either "images" or "videos").

task-3850413

task-3850413

task-3850413

task-3850413

Converted option's extend into a SnippetOption patch.
Adapted refreshPublicWidget.

Note that the signatures had to be adapted to the modern style for
methods that call `super`.

task-3850413

Had to introduce a `multiSequence` because Owl's `setup` is called in
an unpredictable order.

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

Note that the inline-block style is specified only for the customize
tab.

Had to specify a `selectMethod` prop on the parent component so that the
right property name gets used on individual buttons.

task-3850413

task-3850413

task-3850413

task-3850413

This commit converts the ListUserValueWidget to OWL as a WeList
component.
It removes `idMode` from the props (previously dataset) as it was used
because the widget state relied on the DOM, whereas with OWL it is now
the other way around (the DOM relies on the state). It doesn't seem
necessary anymore.

task-3850413

task-3850413

This commit converts the Many2oneUserValueWidget to OWL, into a
Many2oneUserValue and a WeMany2one component.

The template makes an xpath on the template of <WeSelect> as we can't
use the component itself since WeMany2one extends WeSelect.

task-3850413

[REF] web_editor: convert Many2manyWidget to OWL

task-3850413

task-3850413

task-3850413

task-3850413

This commit adds a `notifyOptions` method on the callbacks of the
SnippetEditor to replace the `trigger_up("option_update")` on snippet
options.

task-3850413

This allow options to share a common registry but not interfere with other
modules.

Now, each module will define a "registerOption" method which overrides
the default "module" param.

This approach was chosen to facilitate the ability of some options (like
Parallax) to set itself in between the image options.

These example will be in the following commit

maybe fixup in the conversion of the SnippetOption commit?

task-3850413

task-3850413

task-3850413

# Conflicts:
#	addons/website/static/src/js/editor/snippets.options.xml

[REF] website: convert ScrollButton options to Owl

task-3850413

# Conflicts:
#	addons/website/static/src/js/editor/snippets.options.xml

task-3850413

# Conflicts:
#	addons/website/static/src/js/editor/snippets.options.xml

[REF] website: convert card color option to Owl

task-3850413

task-3850413

task-3850413

This commit fixes a race condition where SnippetEditors are not fully
created and started when updateUI is called by the OWL widgets being
mounted for the first time.

The reason this happens is because when a snippet is dropped, the
SnippetEditors of that snippet are created to call the onBuilt of the
options that match the snippets. However, this is not done inside the
mutex, and therefore, any state update occurring during this situation
could create components that require an updateUI.

The updateUI is done in the mutex so it should almost never conflict
with options not being started, except in this case.

Maybe a better fix would be to add the `callForEachChildSnippet` into
the mutex inside callPostSnippetDrop, but there's probably a reason
why it is not done. So this fix just awaits the postSnippetDropped
promise to delay the call to the mutex.

task-3850413

Attempt at making test_20_snippet_editor_panel_options pass. The issue
is that SnippetsMenu re-render is delayed compared to before, so the
grid button that receives the click is the old one.

task-3850413

task-3850413

task-3850413

This commit converts GalleryHandler, CarouselHandler, GalleryLayout,
Gallery, GalleryImageList, GalleryImage into OWL.

task-3850413

…on (to fixup)

fixup! [REF] web_editor: convert UserValueWidget and <we-button> to OWL

…callbacks

This commit replaces `trigger_up("snippet_option_visibility_update")` on
snippet options with `updateSnippetOptionVisibility()` in the callbacks.

task-3850413

…sibility options

task-3850413

# Conflicts:
#	addons/website/static/src/js/editor/snippets.options.xml

*: website

This refactor was necessary as some option might want to use ORM methods
such as searchRead etc, not just call.

It keeps compatibility with the RPC function as if no env or serviceName
is provided to the function, it will just assume an RPC call.

This commit converts the SocialMedia options to OWL. It also adds a
caching system (`tmpSocialsIds`) to share IDs between the WeList items
and the social snippet's links, so that the OWL state works properly.

task-3850413

task-3850413

task-3850413

This commit adds a way to restrict SnippetOptions to one or several user
groups.
Example of use:

```
registerOption("MyOption", {
	...,
	data: {
		groups: ["website.group_website_designer"],
	},
});
```

task-3850413

task-3850413

task-3850413

# Conflicts:
#	addons/website/static/src/js/editor/snippets.options.js

task-3850413

task-3850413

- Handle triggerWidgetsNames
- Handle onGetCustomColors

task-3850413

*: website_blog, website_event, website_sale

task-3850413

`.s_progress_bar` is already in `so_content_addition_selector` which is
included in `data-selector` and `drop-near`.

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

Also limits old hack approach to non-Owl blocks.

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

*: web_editor
Given that the Donation options used to make a lot of modifications to
the DOM of the `we-list`, all of these have been converted into OWL-
compatible ways of modifying the `WeList` template.
Specifically, we cannot update the UserValueComponent's DOM on the fly
to add new inputs anymore, and we need a proper way to update the value
of the ListUserValue according to the option and vice-versa. Both of
these concerns are addressed by adapting the WeList's template and
adding a new prop `doubleInput`.

task-3850413

task-3850413

task-3850413

Prior to this, when dropping a snippets, its editors would be started
but not added to the DOM, which means that when clicking on it, there
would be a significant delay before options would be accessible.
Note that this delay is present when clicking on a Snippet that is not
dropped for the first time.

The reason for this delay is because even thought the widgets where not
in the DOM, they were still stored somewhere inside the started editor,
reducing the need for renders when clicking on a snippet that was
previously enabled.

This commit tries to mimic the old behaviour by keeping every element in
the DOM and mounted, just hidden with a d-none when the editor is not
currently enabled. This could have some side effects, like in tours
where a SnippetEditor selected is not the one currently visible.

For this reason, this commit is kept separate for now.

…s to Owl

Kept in a separate commit as this fix only makes sense if the changes
that are in the parent commit are accepted

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

task-3850413

Includes header, footer, copyright and theme options.

task-3850413

task-3850413