Steps to reproduce the bug:
- Create a storable product P1 with BoM:
    - Component: Add any component
    - operation: OP1

- Create a MO with P1:
    - Confirm it
    - Start the workorder and mark it as done
- Come back to the dashboard >  workorders list
- Select the finished workorder
- Try to start it

Problem:
The work order can be started while it is in the 'done' state.

When the function `button_start` is called, we will check if we need to
skip the employee check or not. However, since the current user is also
an employee, we will use them:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L258-L259
The function start_employee will then be called:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L284-L286
The state of the work order will then be updated:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L740"

opw-[4024904](https://www.odoo.com/web#id=4024904&view_type=form&model=project.task)

Forward-Port-Of: odoo/odoo#172587

Imagine a scenario where Odoo and Google calendars are synced. Then, this happens:
1. User goes to Google and changes one event from a recurrence series.
2. When saving, user chooses to modify "this event and all upcoming".
3. Odoo syncs from Google automatically via cron.

<details>

```
2024-07-04 10:02:21,094 25 INFO odoo odoo.addons.google_calendar.models.res_users: Calendar Synchro - Starting synchronization for res.users(15,)                                                             
2024-07-04 10:02:21,568 25 INFO odoo odoo.addons.google_calendar.models.calendar_recurrence_rule: Recurrence #4838 | current rule: FREQ=WEEKLY;WKST=MO;UNTIL=20240620T215959Z;BYDAY=FR | new rule: FREQ=WEEKLY;WKST=MO;UNTIL=20240613T215959Z;BYDAY=FR | remaining: 1 | removed: 1                                                                                                                                          
2024-07-04 10:02:21,583 25 INFO odoo odoo.models.unlink: User #15 deleted calendar.event records with IDs: [1999701]                                                                                          
2024-07-04 10:02:21,586 25 INFO odoo odoo.models.unlink: User #15 deleted mail.followers records with IDs: [3665655, 3665656, 3665657, 3665658, 3665659, 3665660, 3665661, 3665662, 3665768]                  
2024-07-04 10:02:21,919 25 ERROR odoo odoo.addons.google_calendar.models.res_users: [res.users(15,)] Calendar Synchro - Exception : Record does not exist or has been deleted.                                
(Record: calendar.event(1999701,), User: 15) !                                                                                                                                                                
Traceback (most recent call last):                                                                                                                                                                            
  File "/opt/odoo/custom/src/odoo/odoo/[api.py](https://api.py/)", line 997, in get                                                                                                                                              
    cache_value = field_cache[record._ids[0]]                                                                                                                                                                 
KeyError: 1999701                                                                                                                                                                                             
                                                                                                                                                                                                              
During handling of the above exception, another exception occurred:                                                                                                                                           
                                                                                                                                                                                                              
Traceback (most recent call last):                                                                                                                                                                            
  File "/opt/odoo/custom/src/odoo/odoo/[fields.py](https://fields.py/)", line 1161, in __get__                                                                                                                                      
    value = env.cache.get(record, self)                                                                                                                                                                       
  File "/opt/odoo/custom/src/odoo/odoo/[api.py](https://api.py/)", line 1004, in get                                                                                                                                             
    raise CacheMiss(record, field)                                                                                                                                                                            
odoo.exceptions.CacheMiss: 'calendar.event(1999701,).write_date'                                                                                                                                              
                                                                                                                                                                                                              
During handling of the above exception, another exception occurred:                                                                                                                                           
                                                                                                                                                                                                              
Traceback (most recent call last):                                                                                                                                                                            
  File "/opt/odoo/auto/addons/google_calendar/models/[res_users.py](https://res_users.py/)", line 100, in _sync_all_google_calendar                                                                                                    
    user.with_user(user).sudo()._sync_google_calendar(google)                                                                                                                                                 
  File "/opt/odoo/auto/addons/google_calendar/models/[res_users.py](https://res_users.py/)", line 79, in _sync_google_calendar                                                                                                         
    synced_events = self.env['calendar.event'].with_context(write_dates=events_write_dates)._sync_google2odoo(events - recurrences, default_reminders=default_reminders)                                      
  File "/opt/odoo/auto/addons/google_calendar/models/[google_sync.py](https://google_sync.py/)", line 181, in _sync_google2odoo                                                                                                          
    odoo_record_write_date = write_dates.get([odoo_record.id](https://odoo_record.id/), odoo_record.write_date)                                                                                                                          
  File "/opt/odoo/custom/src/odoo/odoo/[fields.py](https://fields.py/)", line 1191, in __get__                                                                                                                                      
    raise MissingError("\n".join([                                                                                                                                                                            
odoo.exceptions.MissingError: Record does not exist or has been deleted.                                                                                                                                      
(Record: calendar.event(1999701,), User: 15)
```

</details>

In such case, due to the way this was handled, Odoo would die with `MissingError`.

Here I contribute a test for such scenario and the fix.

@moduon MT-6287





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

Forward-Port-Of: odoo/odoo#172103

**Steps to reproduce the bug:**
- Create a storable product P1.
- Create two purchase agreement with the same product and qty=10

- Create and confirm a PO with only the second PO

- Try to export both purchase agreements, selecting the one without a
PO first and then the other. For the fields to export, choose: Products
to purchase/ordered quantities.

**Problem**:
Sure, here is the corrected version in English:

Both lines will show 0 units. When the `_compute_ordered_qty` is called
with the first PO requisition line, no purchase order is linked, and
therefore the total quantity remains at 0. However, the product is added
as a founded line.
So, on the second requisition line, even though the total quantity (10)
is correctly calculated because a PO is linked, the condition that
checks if the product has already been found will be true, and therefore
the quantity will be set to 0.

https://github.com/odoo/odoo/blob/e7850da5848993e036ab70b731f37005ccd64604/addons/purchase_requisition/models/purchase_requisition.py#L240-L244

opw-[4005265](https://www.odoo.com/web#id=4005265&view_type=form&model=project.task)

Forward-Port-Of: odoo/odoo#171972
Forward-Port-Of: odoo/odoo#171809

Currently a traceback is occurring when the user tries to load demo data in POS.

To reproduce this issue:

1) Install `POS`, `pos_loyalty` without demo data
2) Make sure no products are available in `POS` by disabling
   the `Available in POS` for `products` in the `POS`
3) Now open a session and click the explore `demo data` button

Error:- 
```
KeyError: 'pos_special_products_ids'
  File "odoo/http.py", line 2248, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1823, in _serve_db
    return self._transactioning(_serve_ir_http, readonly=ro)
  File "odoo/http.py", line 1843, 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 1821, in _serve_ir_http
    return self._serve_ir_http(rule, args)
  File "odoo/http.py", line 1828, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2053, 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 756, 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/point_of_sale/models/pos_session.py", line 2127, in load_product_frontend
    return self.get_onboarding_data()
  File "home/odoo/src/enterprise/saas-17.2/pos_preparation_display/models/pos_session.py", line 20, in get_onboarding_data
    result = super().get_onboarding_data()
  File "addons/point_of_sale/models/pos_session.py", line 1902, in get_onboarding_data
    response = self.load_data(['pos.category', 'product.product'], True)
  File "home/odoo/src/enterprise/saas-17.2/pos_settle_due/models/pos_session.py", line 20, in load_data
    response = super().load_data(models_to_load, only_data)
  File "addons/pos_loyalty/models/pos_session.py", line 103, in load_data
    result['custom']['pos_special_products_ids'].extend(
```

When the user clicks on the `load demo` button, it triggers with `only_data` as a truthy value from `[1]`

But the `pos_special_products_ids` value assigns only if no `only_data` from `[2]`

which leads to a traceback from `[3]`

[1]
https://github.com/odoo/odoo/blob/d0cf45dc6bb472907f6b8542992f717c699f5a34/addons/point_of_sale/models/pos_session.py#L1904-L1905

[2]
https://github.com/odoo/odoo/blob/d0cf45dc6bb472907f6b8542992f717c699f5a34/addons/point_of_sale/models/pos_session.py#L289-L307

[3]
https://github.com/odoo/odoo/blob/d0cf45dc6bb472907f6b8542992f717c699f5a34/addons/pos_loyalty/models/pos_session.py#L103-L105

After applying this commit, it will resolve this issue by only accessing the value when the only_data value is falsy.

sentry-5588106710

Forward-Port-Of: odoo/odoo#172608

Steps to reproduce:
- Create a subcontracted bom for a product with:
  - Flexible consumption (with warning)
  - One component requiring 1 qty
- Create a receipt for 10 for that product from the recorded subcontractor
- Click on 'Record Component' and set:
  - Quantity (subcontracted product) to 3
  - Done (component) to 5
- Record Production and validate the warning
- Discard the wizard
- Validate the picking and select 'No backorder'

Issue:
Once validated, the subcontracted consumption will be back to 3 instead of 5.

During the subcontracted move's `_action_done()`, as the move is incomplete, it will be split in two. After doing the split, the `product_uom_qty` of the initial move will be changed to its done quantity, which will trigger the update of the subcontracted demand.

This will end up triggering `change_prod_qty()` of the recorded production, but to change its quantity to the same quantity. However, doing that will reset the consumption of its components to what would be expected from the bom.

Instead of doing that, we can simply stop if there is no quantity to remove anymore before calling `change_prod_qty()`.

opw-4032052

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

Forward-Port-Of: odoo/odoo#172243
Forward-Port-Of: odoo/odoo#171078