[IMP] project: Improve UX
Before this commit:
- project tasks view: when we group by company, milestone, customer,
worksheet template or any m2o field, the KanbanColumnQuickCreate is
displayed for that field, we can add a new one or apply examples,
but thoses examples are stages.
That doesn't make any sens to add them in a project or milestone context,
then if you add a new column manually or via the apply examples, it will
disappear once refreshing the page.
To summarize, stage is the only valid group by that can have the
KanbanColumnQuickCreate.

- all tasks view: same problem as the previous point + quick creating
is also not valid for group by stage as we are in all tasks context that
are linked to different project and the examples are mainly applied for a specific
project, if you try to add manually or via the examples and refresh they are going
to disappear as they are not linked to any project.

- my tasks view, same problem for previous point + quick creating when grouping
by personal stage is valid but apply examples  button is displayed to show stages and if
used, it will not add anything, so it should be hidden.

- Project Kanban examples stages are all created as not folded.
Some users don't know that 'folded in kanban' option is available on the stages,
and that tasks in a folded stage are considered as done.

After this commit:
- project tasks: KanbanColumnQuickCreate and applying examples are only available
when grouping by stage.

- all tasks: KanbanColumnQuickCreate is not available.

- my tasks: KanbanColumnQuickCreate is only available when grouping by personal stages.
applying examples is not available.

- some example stages are folded..

task-3092925

Before this commit:

- The burndown chart displayed the stage in order of the data fetching which wasn't logical especial for a chart that supposed to represent the evolution of the tasks in the project
- When sorting all/my tasks by stage, It was possible to select any project in any quickcreate of the stages which didn't make much sense

After this commit:

The burndown chart legend is now ordered according to the stage sequence (previously was ordered randomly by comming data)
Modified the burndownChartModel, simply makes a RPC to get the stages and sequences then sort the legend elements (one by stage) with it
Display only the projects which uses the stage in the dropdown menu of the task kanban quickcreate (when grouping by stage)

When sorting by all/my tasks by stage, the quickcreate now only display the projects which contains the stage selected
done by adding a domain in the quickcreate form
(shoutout to LTU and AUON who actually found the fix)

Task-3067445

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

[FIX] web_editor: fix some grid layout mistakes/oversights

This commit fixes some mistakes that were found in the code of the grid
layout option. More precisely:

- When a column was dropped near a grid dropzone (so not inside it), and
if its height was bigger than the grid, the `rowCount` attribute of the
row was not updated to the correct number of rows => there was one extra
row.

- When we start dragging a grid item, if we do not go over the starting
grid at all (it happens if the move handle is placed outside of the
row), the `rowCount` of the starting grid was never updated. This is
because the resize is done at the "out" of the dropzone so if there was
no "over", it cannot be done.
=> As a fix, the starting grid is now always resized when we drop the
column.

- When dropping a grid item inside a non-grid dropzone, its `z-index`
CSS property was not removed.

- When a grid item becomes a normal column, when dropping it in a non-
grid dropzone or when toggling the normal mode, the resize classes
(`g-col-lg-*` and `g-height-*`) were not removed from it.

- When a normal column becomes a grid item, the padding and offset
classes were not removed and the `col-` class was not systematically
synchronized with the `g-col-lg-*` class.

=> The two previous points need to be fixed because after doing multiple
drag and drops, the classes could become inconsistent. This happened
especially with columns whose width changes a lot between snippets (like
with Masonry columns, because of the padding).

- When going back to normal mode, the `--grid-item-padding-*` CSS
variables were not removed from the row.

- In the code, the `rowEl` variable is used to have a reference to the
parent of the element we are dragging. In the case of a column, it is
a row but when we drag something else, it may not be the case so naming
it `rowEl` is quite confusing.
=> As a fix, this variable is now called `parentEl` and once we have
checked that it is a row, a `rowEl` variable is declared, referencing to
`parentEl`.

- In commit [1], a comment that should have been modified has been
forgotten.

[1]: https://github.com/odoo/odoo/commit/67d1b078329600efce414974307d74e9fa9ba9fe

task-3151207

--- 
[FIX] web_editor: fix history of a drag and drop after a resize

Steps to reproduce:

​- In a snippet in grid mode, resize a column.

- Drag and drop this column in a non-grid dropzone.

​- Undo.

​=> The column is back in the grid but is still a normal column. The same
happens when doing these steps with a normal column to a grid. 

This happens because the class changes are not observed in these cases.
When fixing the drag and drop history in [2], only the style changes
were observed because the class changes are automatically recorded. But
it is not the case after a resize.

This commit fixes that by also observing the class changes.

[2]: https://github.com/odoo/odoo/commit/1dfb127f70832aa9e9022ac337af343b7dc17729

task-3151207

Forward-Port-Of: odoo/odoo#114818

Steps to reproduce the bug:
- Create a storable product “P1”
1:/
- Select the company A
- Create a purchase order:
    - product: “P1”
    - vendor: “V1”
    - confirm the PO
The vendor “V1” is added to the supplier list of “P1”

2:/
- Select the company B
- Create a purchase order:
    - product: “P1”
    - vendor: “V2”
    - confirm the PO


Problem:
The vendor “V2” is added to the list but “V1” is deleted from the list in company A

The “seller_ids” field is in the “product.template” model, we try to modify it in the “_add_supplier_to_product” function from the “product_id”(product.product) field which inherits from the “product.Template” model:
https://github.com/odoo/odoo/blob/3b88ed5ea458a37ee4d440f83bab45bd0fb13845/addons/purchase/models/purchase.py#L531-L532

So the function “inverse_related” will be called, in which the function “__set__” will be triggered: In the values, the command for the create will be added but the command for the set will be added as well while it shouldn't. So in the `write_real` function a search will be done to get all `product.supplierinfo` with the same product_tmpl_id:

https://github.com/odoo/odoo/blob/36544651f2049bcf18777091dbf02c9631b33243/odoo/fields.py#L4415-L4417

but as we are in sudo, those of company “A” will also be recovered, so they will be unlinked since they are not in the command.set

opw-3251941

Forward-Port-Of: odoo/odoo#117956

Steps to reproduce the bug:
- Go on the blog of the website.
- Edit.
- In the "Customize" section, apply the "List" "Layout" and activate
the "Sidebar".

-> The sidebar appears at the bottom of the page instead of on the
side.

The situation looks like this:
```html
<div class="container">
    <div class="row">
        <div class="col"></div>
        <div class="border-end"></div>
        <div class="col-12"></div>
    </div>
</div>
```
The bug comes from the fact that the `div` with the `border-end` class
is inside a `row` class. Due to that, a bootstrap 5 css rule applies
and puts the `width` of the `div.border-end` element to `100%`. Because
the element tries to fill the entire width of the `div.row`, it is put
at the bottom of the page as well as its following elements (in this
case, the sidebar). By applying an automatic width for the
`.border-end` elements inside `.row` element, the border as well as the
sidebar are displayed as wanted.

opw-3217775

Forward-Port-Of: odoo/odoo#116354

[upg-665618](https://upgrade.odoo.com/web#id=665618&active_id=665618&model=upgrade.request&view_type=form&cids=1&menu_id=107)

When we compute the field_name
[here](https://github.com/odoo/enterprise/blob/saas-16.2/hr_payroll/report/hr_payroll_report.py#L79) if the `code` contains a space (` `) the query will be syntactically incorrect:

```
2023-04-04 12:43:02,182 30 ERROR db_665618 odoo.sql_db: bad query: CREATE or REPLACE VIEW "hr_payroll_report" as (

            SELECT
                p.id as id,
                CASE WHEN wd.id = min_id.min_line THEN 1 ELSE 0 END as count,
                CASE WHEN wet.is_leave THEN 0 ELSE wd.number_of_days END as count_work,
                CASE WHEN wet.is_leave THEN 0 ELSE wd.number_of_hours END as count_work_hours,
                CASE WHEN wet.is_leave and wd.amount <> 0 THEN wd.number_of_days ELSE 0 END as count_leave,
                CASE WHEN wet.is_leave and wd.amount = 0 THEN wd.number_of_days ELSE 0 END as count_leave_unpaid,
                CASE WHEN wet.is_unforeseen THEN wd.number_of_days ELSE 0 END as count_unforeseen_absence,
                CASE WHEN wet.is_leave THEN wd.amount ELSE 0 END as leave_basic_wage,
                p.name as name,
                p.date_from as date_from,
                p.date_to as date_to,
                e.id as employee_id,
                e.department_id as department_id,
                d.master_department_id as master_department_id,
                c.job_id as job_id,
                c.work_entry_source as work_entry_source,
                e.company_id as company_id,
                wet.id as work_code,
                CASE WHEN wet.is_leave IS NOT TRUE THEN '1' WHEN wd.amount = 0 THEN '3' ELSE '2' END as work_type,
                wd.number_of_days as number_of_days,
                wd.number_of_hours as number_of_hours,
                CASE WHEN wd.id = min_id.min_line THEN x_l10n_xx_house rent.total ELSE 0 END as x_l10n_xx_house rent,
                CASE WHEN wd.id = min_id.min_line THEN pln.total ELSE 0 END as net_wage,
                CASE WHEN wd.id = min_id.min_line THEN plb.total ELSE 0 END as basic_wage,
                CASE WHEN wd.id = min_id.min_line THEN plg.total ELSE 0 END as gross_wage

            FROM
                (SELECT * FROM hr_payslip WHERE state IN ('done', 'paid')) p
                left join hr_employee e on (p.employee_id = e.id)
                left join hr_payslip_worked_days wd on (wd.payslip_id = p.id)
                left join hr_work_entry_type wet on (wet.id = wd.work_entry_type_id)
                left join (select payslip_id, min(id) as min_line from hr_payslip_worked_days group by payslip_id) min_id on (min_id.payslip_id = p.id)
                left join hr_payslip_line pln on (pln.slip_id = p.id and pln.code = 'NET')
                left join hr_payslip_line plb on (plb.slip_id = p.id and plb.code = 'BASIC')
                left join hr_payslip_line plg on (plg.slip_id = p.id and plg.code = 'GROSS')
                left join hr_contract c on (p.contract_id = c.id)
                left join hr_department d on (e.department_id = d.id)
                left join hr_payslip_line x_l10n_xx_house rent on (x_l10n_xx_house rent.slip_id = p.id and x_l10n_xx_house rent.code = 'House Rent')

            GROUP BY
                x_l10n_xx_house rent.total,
                e.id,
                e.department_id,
                d.master_department_id,
                e.company_id,
                wd.id,
                wet.id,
                p.id,
                p.name,
                p.date_from,
                p.date_to,
                pln.total,
                plb.total,
                plg.total,
                min_id.min_line,
                c.id)
ERROR: syntax error at or near "rent"
LINE 25: ...WHEN wd.id = min_id.min_line THEN x_l10n_xx_house rent.total...
                                                              ^
```

This is also a security issue, given that it might be used for injection attacks.

The solution proposed here is to replace any space with an underscore (`_`).

Forward-Port-Of: odoo/enterprise#39347

duration_percent field is a stored integer.
In postgresql, integer are 4 Bytes long, which create a range of -2147483648 to +2147483647.
With a small `duration_expected`, and a big `duration`, we can easily break these limits.
This min(max()) limits the range of `duration_percent` between -999999 and 999999.

`duration_percent` is only used in some views as an additional field, ex:
![image](https://user-images.githubusercontent.com/29302288/229797185-775d344f-bb87-4228-9ca2-8fbc19ea54ae.png)
So the impact should be minimal

---

## How to Reproduce:
https://watch.screencastify.com/v/FHPD1qRVYRirO3QgLzCt

- Create a product P1:
    - bom: B1
        - component:  any (bolt / screw)
        - operations: 
             - worcenter: Assembly Line 1
             - default duration: 00:01 minutes
- Create Manufacturing for 1 unit of P1 => PLAN
- On Manufacturing > Work Centers Overview > Assembly Line 1: click on the work order of your MO
- Wait 1 years
- ...
- Ok, just change date_start on the workorder.time_ids to 1 year in the past
- Click on 'Mark as Done'
==> Traceback appear

---

OPW-3253333

Same as: https://github.com/odoo/odoo/pull/117590

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

Forward-Port-Of: odoo/enterprise#39338
Forward-Port-Of: odoo/enterprise#39301