Following https://github.com/odoo/enterprise/pull/96974, we are doing the filtering of rows much later which shows a lot more areas to improve.

First 2 optimizations can be done for *every* report:
<img width="1920" height="296" alt="image" src="https://github.com/user-attachments/assets/6d7e57ce-8b57-4f1c-9ab7-6212495993d3" />
The (1) optimization is to remove the second safe_eval I forgot to remove before :sweat: 
The (2) optimization consist to hash less keys as well as to not iterate over all the lines in _build_lines_columns

Another 2 smaller optimizations are possible on the general ledger:
<img width="1919" height="362" alt="image" src="https://github.com/user-attachments/assets/61d012ee-1014-4d95-82f7-22b0d9c06500" />
<img width="1919" height="426" alt="image" src="https://github.com/user-attachments/assets/eb7e756c-6d3e-4d6b-a445-e0a28aca553c" />
The (3) is outdated
The (4) is `self.env.company.currency_id.id` being accessed

<img width="1919" height="384" alt="image" src="https://github.com/user-attachments/assets/7b945f64-88ac-4ca5-8552-50bdfe17e849" />
(1) is down from 55.42s to 489ms  

(2) is down from ~26s to ~0.55s    
(4) is down from ~4.14s to ~1.9s

*Tests were done on a demo db populated on models res.partner,account.move with a factor of 20000 and opening the Tax Received line of the general ledger which contained about 150,000 lines and a limit_to_load at the default 80*

**Current behavior before PR:**
When a user has previously denied camera or microphone access, the system only shows a warning notification. This makes it unclear for the user how to resolve the issue or where to enable permissions again.

**Desired behavior after PR is merged:**
If the user has already denied access and attempts to use camera or microphone features again, the system now displays a dedicated dialog with an illustration and clear, step-by-step instructions explaining how to re-enable the required permissions from the browser address bar.

Before
<img width="486" height="132" alt="image" src="https://github.com/user-attachments/assets/10a0f7ee-fc50-4e36-bbcc-a6a880d33ca3" />

After
<img width="938" height="488" alt="image" src="https://github.com/user-attachments/assets/da4e361b-7f09-4b06-bb5d-1170c682b4d7" />


task-[5379164](https://www.odoo.com/odoo/project/1519/tasks/5379164)

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

Purpose:
--------
- It should be easier to visualize maintenance requests than what is possible today. The calendar view is useful but does not provide a comprehensive overview of all equipment or work centers, nor the ability to plan interventions easily.
- It should be much easier to perform maintenance directly from an equipment or work center, instead of creating a maintenance request manually.
- It should also be easy to quickly visualize which equipment is currently undergoing maintenance and update their status once the maintenance is completed.

With this commit:
-----------------
- Makes maintenance planning more easier to manage by adding gantt view by equipment/workcenter.
- Replaced the `Maintenance Calendar` menu with `Planning by Equipment` and `Planning by Workcenter`, providing a more practical way to plan maintenance requests by resources rather than relying on the calendar view.
- Allows creating maintenance requests directly from equipment or work center views, reducing manual effort.
- Prevents scheduling conflicts by showing unavailable workcenter intervals due to workorders or non-working hours.
- Removes the `Request Date` field from maintenance requests as it is redundant with `Scheduled Date`; `Scheduled Date` more accurately reflects the intended start of the maintenance request, whereas `Request Date` only indicates when the request was created.
- The Gantt view defaults to filtering records for the respective workcenter/equipment by `Todo` and `Active`, excluding `Done` and `Archived` maintenance requests, to focus on the remaining active requests.
- It also makes other views (e.g., Kanban, List, Pivot, etc.) of Maintenance Requests available alongside the Gantt view
under `Planning by Equipment` or `Planning by Workcenter`, with the default grouping by equipment or workcenter respectively.
- Improve planning by adding a Plan Popup for unscheduled maintenance requests. It is especially useful when maintenance planners have created requests but are not yet sure when they should be scheduled.
- The Plan Popup applies default `Todo` and `Active` filters to prevent accidental planning of cancelled or already repaired requests.

task-4698325