Steps
-----
1. Install accounting and mrp_workorder_hr, activate analytic accounting in
settings.
2. Select a work center and check "Requires Log In"
3. Create a manufacturing order and add a work order using the work center from
the previous step. On the miscellaneous tab, add an analytic account.
4. Confirm the MO.
5. On the Work Orders tab, change the Real Duration to 60:00
6. Analytic account smart button > the gross margin is correctly set.
7. Either change the real duration to 0:00 or open the work order and delete a
line from the Time Tracking tab.
Note: decreasing the Real Duration on the Manufacturing Order page will not lead
to an issue as long as no time record is deleted on the work order (typically,
when decreasing the time by a small amount).

Issue
-----
The gross margin still takes into account the employee's cost for the deleted time.
Note that the workcenter's cost is removed from the gross margin as expected.
Either by _create_or_update_analytic_entry in case the time of the work order
is modified, or unlink if the work order is deleted.
https://github.com/odoo/odoo/blob/16.0/addons/mrp_account/models/mrp_workorder.py

Fix
-----
When deleting a time record, modify the analytic account accordingly.
We create an analytic entry with a previous_duration equal to the
double of the time that is deleted.
https://github.com/odoo/enterprise/blob/a992a3ae345478a148e536103c1585a4caa86113/mrp_workorder_hr_account/models/mrp_workorder.py#L16
That way, we create an analytic entry with a duration equal to the negative
of the deleted time. This will add a positive amount to the analytic
account.
https://github.com/odoo/enterprise/blob/a992a3ae345478a148e536103c1585a4caa86113/mrp_workorder_hr_account/models/mrp_workorder.py#L21-L22
This  makes the analytic account's gross margin consistent with the time
worked.

**opw-3759144**

Forward-Port-Of: odoo/enterprise#58760

[FIX] account_reports: hide lines at 0 when unfold

Problem: There are two way to see the issue :-
                       1- Whenever you go to the balance sheet and check on the hide at 0 option Then you go and
                            unfold-fold-unfold a line with one zero child and non zero child.
                            The line will with zero will keep showing up.
                      2- Mentioned in the task-3898147

Issue: when we check the option 'hide at 0' then we fold and unfold.
           The flow of func 'unfold Loaded Line' (the already loaded lines) has no clue about the 'hide at 0' option
           but on the other hand the func 'unfoldNewLine' (the new added lines) know about the 'hide at 0' option

Solution: Send the lines that we want to unfold to the 'assignLinesVisibility' logic that handle 'hide at 0'
                   as we do with 'unfoldNewLine'
Minor renames: setLineVisibility >> hideZeroLines, assignLinesVisibility >> setLineVisibility

Task-3898147

This error arises when the someone clicks on ``Early Discount`` in Payment Terms while creating a new one.

Steps to reproduce
- Install ``account`` module
- Invoicing -> Configuration -> Invoicing -> Payment Terms
- Click on ``New`` -> click on ``Early Discount``

Traceback : 
```
ValueError: not enough values to unpack (expected 1, got 0)
  File "odoo/models.py", line 5848, in ensure_one
    _id, = self._ids
ValueError: Expected singleton: res.currency()
  File "odoo/http.py", line 2251, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1827, in _serve_db
    return self._transactioning(_serve_ir_http, readonly=ro)
  File "odoo/http.py", line 1847, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 134, in retrying
    result = func()
  File "odoo/http.py", line 1825, in _serve_ir_http
    return self._serve_ir_http(rule, args)
  File "odoo/http.py", line 1832, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2057, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 220, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 739, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 38, in call_kw
    return self._call_kw(model, method, args, kwargs)
  File "addons/web/controllers/dataset.py", line 34, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 458, in call_kw
    result = getattr(recs, name)(*args, **kwargs)
  File "addons/web/models/models.py", line 1011, in onchange
    todo = [
  File "addons/web/models/models.py", line 1014, in <listcomp>
    if field_name not in done and snapshot0.has_changed(field_name)
  File "addons/web/models/models.py", line 1127, in has_changed
    return self[field_name] != self.record[field_name]
  File "odoo/models.py", line 6576, in __getitem__
    return self._fields[key].__get__(self, self.env.registry[self._name])
  File "odoo/fields.py", line 1261, in __get__
    self.compute_value(recs)
  File "odoo/fields.py", line 1443, in compute_value
    records._compute_field_value(self)
  File "odoo/models.py", line 4931, in _compute_field_value
    fields.determine(field.compute, self)
  File "odoo/fields.py", line 100, in determine
    return needle(*args)
  File "addons/account/models/account_payment_term.py", line 95, in _compute_example_preview
    discount_amount = record._get_amount_due_after_discount(record.example_amount, 0.0)
  File "addons/account/models/account_payment_term.py", line 67, in _get_amount_due_after_discount
    discount_amount_currency = self.currency_id.round(total_amount - (total_amount * (1 - (percentage))))
  File "odoo/addons/base/models/res_currency.py", line 217, in round
    self.ensure_one()
  File "odoo/models.py", line 5851, in ensure_one
    raise ValueError("Expected singleton: %s" % self)
  ```

This error occurs from line[1] where the currency ID is getting false within the self, leading to a value error being raised. This happens because of this PR https://github.com/odoo/odoo/pull/161044, where they have removed the default currency from currency ID field.

This commit will fix the above error by adding ``company_id`` field in the payment term from view.

[1] : https://github.com/odoo/odoo/blob/5673ea9d8c6993575bd9ce9c2a931a8738e77e76/addons/account/models/account_payment_term.py#L67

sentry - 5209971284


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

Since commit [1], a fake unit can be specified on `InputUserValueWidget` widgets, thanks to the `data-fake-unit` attribute. It allows to display a unit whose purpose is only to show a dummy unit and which does not need to be converted to other ones.

However, it is still a unit, so the value written in the input should still be considered as numeric and should therefore be processed as such (e.g. checking if it has the correct format or if it is well a number). This is currently not the case, since only values with real units (i.e. with `data-unit`) allows to go through these checks. This means that fake unit inputs can accept any values, which can cause errors if only numeric ones were expected (e.g. for numeric CSS properties).

The same goes for inputs without unit but still having a step specified. Indeed, the `data-step` attribute allows to increase/decrease the value by using the keyboard arrows, which implies that the value should be considered as numeric. Note that no option is really broken by that, as they generally either parsed the value themselves or accepted the value without any traceback assuming that the user should write logical values and should not be surprised if it does not work. But the comma use case makes it worth being fixed.

This commit adds the fake unit and step cases to the checks, so the input values are considered as numeric and can properly be parsed to numbers.

Steps to reproduce:
For the fake unit case:
- In website edit mode, go to the "Theme" tab in the right panel.
- In the "Paragraph" section, set the "Line Height" option to a decimal number but with a comma instead of a period.
- Save. 
=> There is a style compilation error, because the value was used as is in the CSS file, which is not correct. If it was a real unit, the value would have been cut before the comma by the `parseFloat` function.

For the step case:
- In edit mode, drop the "Form" snippet.
- Add a new field and set its "Type" option to "File Upload".
- Set the "Max # Of Files" option to a decimal number but with a comma.
=> If we wrote a number bigger than 1 to allow uploading multiple files, the field will stay as a single file input.

[1]: https://github.com/odoo/odoo/commit/388e4bb2bfcaebdd4ff30277fb49a034592d7086

opw-3635886

Forward-Port-Of: odoo/odoo#163160