#### Description of the issue/feature this PR addresses:

When updating an allocation's number_of_days, a validation check is performed to ensure that we do not reduce the `number_of_days` to be less than the number of leaves that are taken by the employee. However this logic also takes into consideration any virtual leaves (leaves that are in the `confirm` or `validate1` state, ie. leaves that are awaiting an approval)  that may have been requested by an employee. These virtual leaves that are not yet approved should not count towards the calculation since it could be possible that the employer could refuse them or the employee's accrual plan could grant sufficient leaves if it is requested for a future date.


#### Current behavior before PR:

1. Setup a timeoff type that requires approval from the manager
2. Set up an accrual plan where an employee accrues '_N_' days of leave at the start of each year with **no carryover** (NOTE: the no carryover is the most crucial step because this is what writes the number_of_days on the leave allocation to zero)
3. Request a leave by an employee for any date after the carryover period.

What should have happened: The accrual should reset the leaves based on no carryover policy back to _N_ days 
However, it throws a validation error:

Now the issue happens because when we see that the carryover is none because of which:
1. The allocated leaves are set to 0 when calling this CRON (for no carryover): https://github.com/odoo/odoo/blob/cf18c4ac88919513a9f2b922d625fa5dc113cb39/addons/hr_holidays/models/hr_leave_allocation.py#L527
2. The leave that was requested by the employee but not yet approved causes the validation to fail. It is best explained in the below screen recording which uses the test case mentioned in the commit:

https://github.com/user-attachments/assets/f8914bac-815d-48c9-b4b2-c132a2fccbdb

![image](https://github.com/user-attachments/assets/cc2e221d-a725-4e9e-aaee-a054f644dff6)
![image](https://github.com/user-attachments/assets/8522bc81-5416-4bf0-ac71-bea1d2a133b8)


#### Desired behavior after PR is merged:

Virtual Leaves that are not yet approved would not block us from updating the allocation's `number_of_days`

opw-4442471

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

Forward-Port-Of: odoo/odoo#200404
Forward-Port-Of: odoo/odoo#198382

Description of the issue/feature this PR addresses: Spurious log entries

Current behavior before PR: Odoo [logs](https://github.com/odoo/odoo/blob/17.0/odoo/modules/registry.py#L653-L654) indexes created by [_sync_plan_column](https://github.com/odoo/odoo/blob/17.0/addons/analytic/models/analytic_plan.py#L281) as unexpected

Desired behavior after PR is merged: No log entry for expected index

Steps to reproduce:

- create a new analytic plan, ie 'Test plan'
- go to technical/database structure/fields, search for the custom field created on model account.analytic.line, named `x_plan{the id of the plan you created in step 1}_id`
- observe the field is not marked as indexed, even though the code creates an index
- update the analytic module, observe there will be an entry of the form `Keep unexpected index account_analytic_line__x_plan{the id of the plan you created in step 1}_id_index on table account_analytic_line`

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

Forward-Port-Of: odoo/odoo#200764
Forward-Port-Of: odoo/odoo#189240

### Steps to reproduce:
	- create a new quotation with configured quotation template
	- the descriptions are added by default (thanks to the template)
	- confirm the SO
	- the task is created, but it shows the description in the title (instead of the name of the product) and the description tab is empty

### Cause:
In 'Quotation Templates' the description of each line is being stored under the name of 'name' so when using this quotation template in an SO the SO line name will be the template line name not the product name + the description and so when creating the task we use the name of the SO line which in that case will be the description.

### Fix:
We are checking if we have a quotation template or not and if we don't we use the name of the SO line to get the name and the description of the task if we have a quotation template we use the product name for the name of the task and the name of the template line as a description.

opw-4482867

Forward-Port-Of: odoo/odoo#195649

Currently, an exception is raised when the user clicks on the catalog in a quotation if a product has no assigned category.

Steps to Reproduce:

1. Install the sale_management module.
2. Navigate to Sales -> Configuration -> Settings.
3. Enable the Pricelists.
4. Open a new Pricelists -> Add a Price Rules with Apply To `Category`, select a category, and save.
5. Go to Products -> Products.
6. Open an existing product and remove its product category.
7. Go to Sales -> Orders -> New Quotation.
8. Select the created Pricelists, and click on Catalog.
9. An error occurs.

Error:
`AttributeError
'bool' object has no attribute 'startswith'
`

This issue [1] occurs because when the user tries to access product category, the product category is not provided, as it is not a required field.

[1] -
https://github.com/odoo/odoo/blob/4bf8fc4c43ab7d8fd923aaaea8c6423c9a16e428/addons/product/models/product_pricelist_item.py#L481

This fix resolves the issue by ensuring that the product category exists before trying to access it.

sentry-6320016916

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

Forward-Port-Of: odoo/odoo#200306

Currently, an error occurs when while adding a private/public key in the certificate and key has no 'content' (Key file).

Step to produce:

- Install the ```certificate``` module.
- Go to Settings, Click on 'certificates' which is in the Certificates and Keys section
- Create a new certificate, add a name and valid certificate file.
- Create a ```Private Key``` or ```Public Key``` from the certificate form view and try to save the record.

```TypeError: argument should be a bytes-like object or ASCII string, not 'bool'```

An error occurs because a user can directly create a certificate's private/public key from the certificate form view without adding any content that is required true in ```certificate.key``` model, so an error occurs when the system tries to decode the content of private/public key at [1], but it is not available.

Link [1]: https://github.com/odoo/odoo/blob/2be7f413493a6ad43980eb031b8383deb3a706c0/addons/certificate/models/key.py#L157-L160

To resolve this issue, remove the 'create' option for private/public keys from certificate form view

Sentry-5993525387

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

Forward-Port-Of: odoo/odoo#183870

Before this commit, when the user creates a custom filter in SO model to
select the SO in which there is at least one task linked to a specific
project, he got an error saying the domain is invalid.

This commit fixes the issue by improving the search method implementing
for the `task_ids` field to make sure the search view supports a query
contained inside `value` parameter.

Steps to reproduce the issue:
----------------------------

0. Install `sale_timesheet` module with demo data
1. Go to Sales app
2. Creates a custom filter and select `Tasks associated to this sale >
   Project` as left part, `=` as operator (second field in the custom
   filter) and `After sales-service` as project (right part, last field
   in the custom filter).
3. Apply the custom filter

Expected behavior:
-----------------

The custom filter should be applied without any issue.

Current behavior:
----------------

The user has an error saying the domain is invalid when he tries to
save/apply his custom filter.

Forward-Port-Of: odoo/odoo#200975
Forward-Port-Of: odoo/odoo#200130

Currently, when `marketing_automation_whatsapp` is installed, marketing automation campaign statistics are not computed correctly.

### Steps to Reproduce

1. Install `marketing_automation_whatsapp`.
2. Create a marketing automation campaign with an email activity.
3. Ensure one or more traces are rejected (e.g., by using invalid email addresses).
4. View the activity statistics.

Expected Result:
The rejected count on the right correctly displays the number of rejected traces.

Actual Result:
The rejected count on the right always displays `0`, even when rejected traces exist.

### Cause

The `marketing_automation_whatsapp` module overrides `_get_full_statistics` to include WhatsApp-related statistics in addition to the marketing data. However, the override currently concatenates the results from the base `_get_full_statistics` and the WhatsApp-specific statistics. And because `MarketingActivity._compute_statistics` doesn't expect `_get_full_statistics` to return multiple entries for a given `activity_id`, the values from the WhatsApp-specific results end up overwriting the base values.

opw-4292488
opw-4523885
opw-4585705
opw-4585779

Forward-Port-Of: odoo/enterprise#79348

This commit restores the position of the working schedule dropdown to be just below the label in the salary configurator, like in previous versions.
![image](https://github.com/user-attachments/assets/6465e9b1-05ef-4661-a768-13fa386118f6)
The cause of the issue is that the SelectMenuWrapper component is attached just after the invisible select element: https://github.com/odoo/enterprise/blob/9f6a4f0697edcc9330ad7976c6602d892e7b6ef9/hr_contract_salary/static/src/js/hr_contract_salary.js#L69-L71 But before other elements are placed in the DOM between them.

A solution is to add a wrapper div around the selection, ensuring the `SelectMenuWrapper` component is attached inside that div, and further elements placed in the DOM after the wrapper div.

**Steps to reproduce**
- Install hr_contract_salary_payroll
- Select any employee contract > Generate offer > Salary configurator
- Add `part?=80` (any value != 100) at the end of URL

opw-4496279

Forward-Port-Of: odoo/enterprise#79966

Purpose
=======
In the Facebook settings, a user can ask an application (eg Social) to remove his data.

If the deletion is not implemented, it should be done manually for each user, and so we want to automate that process.

Technical
=========
The deletion process is done in that order:
1. The user go to his settings and ask Odoo to remove the data we have
2. Facebook will hit an endpoint in IAP, with a signature, and the  Facebook user id
3. IAP will reach the database, (with a shared secret to authenticate itself) and that endpoint will remove the social accounts, and also the social posts / templates if the account is selected

We do it that way, instead of having a CRON on the client database, because we are able to know if the user uninstalled social, or if he already removed the account.

If the database is not reachable from the internet, we will have it's dbuuid, and so, we will be able to take an action.

Authentication
==============
IAP needs to authenticate to the Odoo database,
so both need to share a secret.

That secret can not be the extended token,
because we don't store it on the Odoo side.

That secret is derived from the database secret, and sent when we ask the Facebook URL (in python, without a browser redirection), so the social user can not see it (otherwise, he will be able to bypass company access rules, and delete the social accounts of different company).

Setup
=====
1. Start Odoo and IAP instances
2. Start ngrok on the IAP port
3. In the Facebook settings ("Facebook Login For Business" -> Settings)
    - Add <ngrok_url>/api/social/facebook/1/callback in the Facebook settings
    - Add <ngrok_url>/api/social_facebook/1/deletion_callback in the Facebook settings
4. Add the Facebook credentials in the IAP settings
5. In the Odoo db, add the system parameter `social.social_iap_endpoint` with the ngrok url
6. In the IAP db, change the system parameter `web.base.url` with the ngrok url
7. In the IAP code, in `facebook_controller.py`, comment the dbuid check `_check_has_access`
8. Add your accounts
9. Go to `https://www.facebook.com/settings/?tab=business_tools`, and remove the app
10. Go to the "Removed" tab, then "View Details" and click on "Send Request"

Task-4350697

Forward-Port-Of: odoo/enterprise#79992
Forward-Port-Of: odoo/enterprise#74865