This commit's purpose is to fix the display of progress bar in the gantt view.

before this commit:
When the planning view is grouped by project, the progress bar is not correctly displayed for some project

after this commit:
The progress bar is now correctly displayed

step to reproduce:
- go to the project setting
- enable the planning option
- open the planning app
- click on the 'schedule by project' menu The progress bar of project with allocated hours but without any slot on the date range of the view is not displayed.

solution:
update the data send to the js rpc call of the gantt_progress_bar method.

detail of the implementation:
The dict send to the javascript side is created in the method gantt_progress__bar_project_id of the 'planning.slot' moduel. It used to only use the result of the read_group of the 'planning.slot' to create the return values. It was updated to also take into account the project that were not in the read_group result.

task - 3485773

Forward-Port-Of: odoo/enterprise#49183
Forward-Port-Of: odoo/enterprise#46638

When the user analyzes the "Timesheet and Planning Analysis" pivot report from the project module and adds it to the "Timesheet vs Planning" filter from the Favourites at the time traceback was generated.

Steps to reproduce:
- Install the "project_timesheet_forecast" module.
- Project > Reporting > Timesheet and Planning Analysis
- Click on the pivot icon and add it to the "Timesheet vs Planning" filter from the Favourites.
- After that, a traceback will be generated.
- Error: ValueError: Invalid field 'date' on model 'project.timesheet.forecast.report.analysis'

As per the base code, the "date" invalid field existed in the user-defined filter context, so when the user tried
to analyze the "Timesheet and Planning Analysis" pivot report and add to the "Timesheet vs Planning" filter from
the Favourites at the time, a traceback was generated. The "date" field does not exist in the "project.timesheet.forecast.report.analysis" object, so instead of the "date" field in this filter, We used the "entry_date" field.

Code reference:
https://github.com/odoo/enterprise/blob/91426a8c4cfd26a5b8eadeafaf4687e47b7366e3/project_timesheet_forecast/report/timesheet_forecast_report.py#L16


Sentry Traceback:
```ValueError: Invalid field 'date' on model 'project.timesheet.forecast.report.analysis'
  File "odoo/http.py", line 2134, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1710, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "odoo/service/model.py", line 133, in retrying
    result = func()
  File "odoo/http.py", line 1737, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1938, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "addons/website/models/ir_http.py", line 233, in _dispatch
    response = super()._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 191, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 717, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 30, in call_kw
    return self._call_kw(model, method, args, kwargs)
  File "addons/web/controllers/dataset.py", line 26, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 457, in call_kw
    result = _call_kw_model(method, model, args, kwargs)
  File "odoo/api.py", line 430, in _call_kw_model
    result = method(recs, *args, **kwargs)
  File "home/odoo/src/enterprise/saas-16.4/project_timesheet_forecast/report/timesheet_forecast_report.py", line 144, in read_group
    return super().read_group(domain, fields, groupby, offset=offset, limit=limit, orderby=orderby, lazy=lazy)
  File "odoo/models.py", line 2513, in read_group
    raise ValueError(f"Invalid field {field_name!r} on model {self._name!r}")
```


sentry-4410474697

Forward-Port-Of: odoo/enterprise#46203
Forward-Port-Of: odoo/enterprise#46088

This fix is necessary for this PR: https://github.com/odoo/odoo/pull/135865

Because the "test_multiple_fsm_task"  fails at this line: https://github.com/odoo/enterprise/blob/16.0/industry_fsm_stock/tests/test_fsm_stock.py#L739-L740

When the "action_fsm_validate" function is called, the "qty_delivered" is computed:

https://github.com/odoo/enterprise/blob/0025b1295319f69feb70d5cb5ec80acf92d76ec9/industry_fsm_sale/models/project_task.py#L236

https://github.com/odoo/enterprise/blob/21ba5cca5107f2ac16e956d669338ecb44622d00/industry_fsm_stock/models/project_task.py#L32

https://github.com/odoo/enterprise/blob/21ba5cca5107f2ac16e956d669338ecb44622d00/industry_fsm_stock/models/project_task.py#L41

However, in the "_compute_qty_delivered" function, since the moves are in the "confirmed" status, the "qty_delivered" is set to 0:

https://github.com/odoo/odoo/blob/8a3284685856b6980e3b620abdbbb3e2c79f57c4/addons/sale_stock/models/sale_order.py#L215

But then, this quantity is modified with "so_line.product_uom_qty":

https://github.com/odoo/enterprise/blob/21ba5cca5107f2ac16e956d669338ecb44622d00/industry_fsm_stock/models/project_task.py#L65-L66

However, since move lines are created  afterward:
https://github.com/odoo/enterprise/blob/21ba5cca5107f2ac16e956d669338ecb44622d00/industry_fsm_stock/models/project_task.py#L67

The "qty_delivered" field must be recomputed because it now depends on "qty_done."

But since the moves remain in the "confirmed" status, the "qty_delivered" is set to 0, whereas it should remain at 2

**Solution:**

Set the "qty_delivered" with "so_line.product_uom_qty" after the creation of move lines. This way, the "compute_qty_delivered" will not be triggered.

OPW-3504138

Forward-Port-Of: odoo/enterprise#48500
Forward-Port-Of: odoo/enterprise#48246

Steps to reproduce:
- Install Accounting, Sales, Contacts & AvaTax
- Setup AvaTax in Accounting settings
- Activate CAD currency
- Create a CAD pricelist
- Create a fiscal position:
  * Use AvaTax API: checked
  * Detect Automatically: checked
  * Country: Canada
- Create a Canadian contact: (e.g. Contact X)
  * Street: 2 Rue des Jardins
  * City: Quebec
  * State: Quebec (CA)
  * ZIP: G1R459
  * Country: Canada
- Create a product with "[FR] Shipping only common carrier - fob destination (backward compatibility)" as Avatax Category. (e.g. Product X)
- Create a SO:
  * Customer: Contact X
  * Pricelist: CAD pricelist
  * Order Lines:
    - product: Product X
    - Unit Price 100.00
- Save SO
- Click on "COMPUTE TAXES USING AVATAX"
- => 2 taxes are added ("CANADA GST/TPS [CA] (5.0000%)" and "QUEBEC QST/TVQ [QC] (9.9750%)"). The 2nd one is exempted. So the total taxes are 5.00.
- Confirm SO
- Deliver the product if needed
- Create an invoice from SO (Regular invoice)
- Click on "COMPUTE TAXES USING AVATAX"

1st issue:
The total taxes are 14.98, which are different from the taxes computed in SO (i.e. 5.00).
The exempted tax is not exempted in the total taxes of the invoice.

2nd issue:
When checking the tax lines in "Journal Items" tab, we can see that the amounts of the debit/credit columns are not consistent.
For "CANADA GST/TPS [CA] (5.0000%)" tax, the credit has the same value than the absolute value of "Amount in Currency", when the currency rate should be applied.
For "QUEBEC QST/TVQ [QC] (9.9750 %)" tax (that should be exempted), debit and credit are 0, but "Amount in Currency" is not.

Cause:
When checking if the tax should be manually fixed, we are comparing tax line balance with the amount provided by AvaTax.
However, these 2 amounts are not always in the same currency. Also, when fixing the tax amount manually, amount_currency field is not updated and debit/credit fields are updated with the values coming from AvaTax without conversion to the company currency.

opw-3439742

Forward-Port-Of: odoo/enterprise#49292
Forward-Port-Of: odoo/enterprise#48221

Steps:
	- Install sign
	- Install `FreeSerif` font (with `apt-get install fonts-freefont-ttf` for example)
	- Use custom font with system parameter key: `sign.use_custom_font` and value: `FreeSerif`
	- Upload a new pdf in sign module
	- Add a new item type Selection
	- Add two options in the previous item one with special chars for example `ąčęėįšųūž`
	- Click `Sign now`
	- Select a random option in the previously created selection item
	- Sign In the navigator pdf viewer special chars string is correctly rendered This is not the case in the downloaded document

Cause:
Selection item is rendered using a `Paragraph` (from `reportlab` lib). The problem is this `Paragraph` uses a different stylesheet given by `getSampleStyleSheet()["Normal"]` defined in the `reportlab` lib here
```py
    stylesheet.add(ParagraphStyle(name='Normal',
                                  fontName=_baseFontName,
                                  fontSize=10,
                                  leading=12)
                   )
```

https://github.com/eduardocereto/reportlab/blob/master/src/reportlab/lib/styles.py#L251-L255

but it doesnt use the right font, this commit use a custom `ParagraphStyle` with the right font and size

Forward-Port-Of: odoo/enterprise#49106
Forward-Port-Of: odoo/enterprise#48422