This fix resolves an issue where orders with zero total amount were not being processed correctly in the kitchen display system. Previously, the confirmation page would not display and orders would not be sent to the preparation display when the order total was zero. Now, all orders—regardless of their total amount—are properly confirmed and routed to the kitchen display for preparation.

The confirmation page wasn't displayed and the order wasn't sent to the
preparation display when confirming an order with a total of 0.

Now the confirmation page is displayed and the order is send to the
preparation display when the order is confirmed regardless of the total
amount.

Fixed an issue where customers completing free orders (with $0 total) in the self-service point of sale system were not seeing the confirmation page or having their orders sent to kitchen preparation. Now all orders, regardless of total amount, properly display confirmation and route to preparation as expected.

The confirmation page wasn't displayed and the order wasn't sent to the
preparation display when confirming an order with a total of 0.

Now the confirmation page is displayed and the order is send to the
preparation display when the order is confirmed regardless of the total
amount.

This fix resolves a system crash that occurred when clicking the sales order button in project updates. The issue happened when certain data values were missing or null, causing the application to fail. The fix ensures the system handles these missing values gracefully by setting them to a default state, allowing users to view sales order information without interruption.

Step to Reproduce :
-> Create product: Project & task
-> Create SO > Add product > Confirm it
-> Go to Newly created project > Project update > Sales order
-> Click on the project stat button > again go to project status > Sales Order
-> Crash it

Before these commit:
-> Clicking on so stat button in project update caused a traceback error that 
null value is not defined.
-> When we are passing the context It was observed that create key 
has null value in that context.
-> In sale_project if create_for_project_id has a null value then create key 
also have null value.

After these commit:
-> So if we set False in the context, If we get null value of create key 
it is set to False.   

task- 3586341

Forward-Port-Of: odoo/odoo#153780

This fix corrects how timesheet entries are processed when employees take global time off. Previously, timesheet lines for projects linked to global time off periods were being incorrectly included in calculations. Now they are properly filtered out, ensuring accurate timesheet reporting and payroll processing during company-wide holidays or closures.

Fix to avoid considering TS lines for projects linked to global time off

Forward-Port-Of: https://github.com/odoo/odoo/pull/156338

Forward-Port-Of: odoo/odoo#157108

A previous update to the product expiry module changed how data is organized for barcode labels, but didn't update all related templates that depend on this data. This fix ensures all barcode label templates use the correct data structure so labels print properly.

The previous fix ae3ec529c77779d08e5e1728a0c4a6afa5cb8bcf introduced a dict to display the values required in the zpl label template.
This change didn't also update the template inheriting this one, hence the need for this fix.

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

Forward-Port-Of: odoo/odoo#157106

This fix improves the performance of saving customer edits in the Point of Sale system. Previously, when saving a customer's information, the system would reload data for all customers in the database, which could slow down the database server. Now it only reloads the specific customer being edited, making the operation faster and more efficient.

Issue -->

`saveChanges` at https://github.com/odoo/odoo/blob/6fc1f1c146b1385f9acf53c8fe69c3877cea32d5/addons/point_of_sale/static/src/js/Screens/ClientListScreen/ClientListScreen.js#L155-L165 calls `load_new_partners` that calls `prepare_new_partners_domain` to compute the domain on which the `res.partner` model is to be searched on, after the save has been commited.
 The search is done to update client-side `res.partner `data.

Domain in question --> https://github.com/odoo/odoo/blob/5404f3367a611e527fcecc2dd49e683864ba4b81/addons/point_of_sale/static/src/js/models.js#L784

This domain has the potential to make `search_read` return every `res.partner` record and compute fields such as `total_due` on each one of them. This presents the issue of overworking postgres when we only need to update one `res.partner` record.

Solution -->

Use the `_loadPartners` method instead to only reload the current partner being edited + saved.

opw-3619941

Forward-Port-Of: odoo/odoo#156841
Forward-Port-Of: odoo/odoo#155141