## [FIX] web_hierarchy,hr_org_chart: move specific changes in hr_org_chart

Before this commit, some recent changes altered the generic view for
Org Chart view of `hr.employee` model. The problem is those changes
also altered the other hierarchy view used in others models.

This commit moves the recent specific changes to hierarchy view
of `hr.employee` model to be sure to alter only the org chart view
of that model.

## [FIX] web_hierarchy: detect cyclic before altering the parent field

Before this commit, the user could drag the first employee displayed
in the gantt and drop him on one of his subordinate. By doing that,
the manager of that employee will be his subordinate and a cyclic
will occur and no record will appear when the org chart will be
reloaded because no employee will have no manager set.

This commit fixes the issue by improving the cyclic detection when
the user uses the drag and drop feature. That is, the action will be
blocking when the system detects the user tries to drag and drop a manager
to one of his subordinates.

This PR contains two commits each of which has a different purpose :

---

The first commit is a cleanup of the Aged Payable audit as it can be improved a lot by using the new "action_audit_cell" method callable on any report. It is also done in order to fix an unwanted behavior on the Aged Receivable report where no amounts would appear in the different cells of the report.

Find more information about it in the first commit's message

---

The second commit makes the Aged Receivable report auditable as well. The current behavior of the Aged Receivable is not to be auditable but the way the audit of the Aged Payable has been made makes it easy for the Aged Receivable to be auditable as well so let's do it.

Find more information about it in the second commit's message.

---

After both these commits are merged, the Aged Receivable report's cells show the amounts they are supposed to at every time, the Aged Payable report's audit system is cleaner and the Aged Receivable is now auditable.

When a user changes product type of a service type product which is used in a sale order and then try to access helpdesk ticket linked to that sale order, the error is generated.

Steps to reproduce:
- Install helpdesk_sale_timesheet module.
- Create a sale order by selecting a customer and adding product 'Customer Care (Prepaid Hours)' (which is a service type product) and click on confirm button.
- Now create a helpdesk ticket in VIP SUPPORT and select the same customer and sale order which you have created.
- Now again go to same sale order and click on 'Customer Care (Prepaid Hours)' product and change its type to 'consumable' from 'service', a warning will occur close it and click on save button.
- Now click on helpdesk ticket smart button, the error will occur.

Error: 
```
  File "odoo/http.py", line 2139, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1715, 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 1742, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1943, in dispatch
    result = self.request.registry['ir.http']._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 34, in call_button
    action = 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 466, in call_kw
    result = _call_kw_multi(method, model, args, kwargs)
  File "odoo/api.py", line 453, in _call_kw_multi
    result = method(recs, *args, **kwargs)
  File "home/odoo/src/enterprise/saas-16.4/helpdesk_sale_timesheet/models/sale_order.py", line 37, in action_view_tickets
    default_sale_line = next(sol for sol in sorted_line if sol.product_id.detailed_type == 'service')
StopIteration: null
```

The error is occurring because the iterable has reached to its end in next function when condition in it is getting False over here - https://github.com/odoo/enterprise/blob/1188db8cba436b887331bef8e07f6f1fafbe1982/helpdesk_sale_timesheet/models/sale_order.py#L37

To solve this error we are giving default value to next function.

sentry-4560590481

Forward-Port-Of: odoo/enterprise#49593

Steps:
- Open Field service
- Select All task
- Create task from kanban view
- The partner_id field is missing and
- Task isn't being created in the selected stage

Issue:
- When trying to create a task from the Kanban view using quick create, the 'partner_id' field is missing in the Kanban box
- In quickcreate the task isn't being created in the selected stage

Cause:
- In the QuickCreate form view, replace the project_id field with regard to the raised issues

Fix:
- The partner_id field is already mentioned in the parent view, but project_id replaced that field in this view. After removing project_id, the parent view will be restored, and the partner_id will be visible

- Before that the project_id is replaced from form view, it means we skip that field from the form view,it will not be considered as the project_id. But, we need the project_id for setting the default_stage_id in the Kanban view, But We don't need it to be visible in the form view, That's why project_id is invisible.

task-3522178

Forward-Port-Of: odoo/enterprise#48653