Currently an error occurs when user removes the invisible condition on vendor bill smart button and click on it.

Steps to replicate:
- Install purchase, web_studio with demo.
- Open any purchase order and turn on studio mode.
- From the View tab click `Show invisible Elements`.
- Remove the invisible condition from the vendor bill smart button.
- Turn off the studio mode and click on the vendor bill smart button.

Error:
```
  File '/home/odoo/odoo19/community/addons/purchase/models/purchase_order.py', line 963, in action_view_invoice
    result['context'] = literal_eval(result['context'])
                                     ~~~~~~^^^^^^^^^^^
KeyError: 'context'
```

Cause:
- Since the user removed the invisible condition from the Vendor Bill smart button, the button becomes visible even when there is no bill linked to the purchase order.
- As a result `invoices` is received as `False` as there is no linked vendor bill the `else` branch gets evaluated [1], which completely overrides the original `result` (window action). As a consequence, when trying to access `result['context']` we get this error.

Solution:
- Returned from the function when the action type is `act_window_close` as it doesnt make sense to add any context to it.

[1]: https://github.com/odoo/odoo/blob/6f2930dcaf202c8e034e958c0a2868e7802578b2/addons/purchase/models/purchase_order.py#L960-L961

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

**Steps to Reproduce:**
-  Create a Server Action of type 'Webhook Notification'.
- Select a model containing a field that returns a `frozendict`-based structure (e.g. `account.move` → `needed_terms`).
- Add the field to the webhook fields.
- Open the webhook sample payload preview.

**Issue:**
- During sample payload generation:
   - The selected fields are read from a sample record.
   - A selected field returns a structure containing `frozendict` objects.
   - The payload is serialized using `json.dumps()`.
   - JSON serialization fails with:
```text
TypeError: keys must be str, int, float, bool or None, not frozendict
```
  - The webhook sample payload computation crashes and the preview cannot be displayed.

**Root Cause:**
- The webhook sample payload may contain `frozendict` objects returned by selected fields.
- The serializer used for payload generation does not handle such mapping-like objects, causing  `json.dumps()` to fail.

**Solution:**
- Use a serializer that converts mapping-like objects into JSON-compatible structures before serializing the webhook sample payload.

**OPW-6295777**

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#271864

The chatter recipients input always added a "Create" option to its autocomplete dropdown, even when the field held no text. The feature that introduced this input, https://github.com/odoo/odoo/commit/3b985d2c4239fe702c1a56bef04fc112af39e954, wired that option to create a res.partner straight away. Selecting "Create" with an empty input therefore created a partner with no name, displayed everywhere as "Unnamed".

The email popover that opens for a recipient without an address then offered a Discard button, but the empty partner was already saved. The same sequence could be repeated to accumulate nameless contacts, which later raise a missing name error when opened in the Contacts app.

Only add the "Create" option when the typed term resolves to a name or an email, in getAutoCompleteSources of recipients_input.js. An input with no usable text has nothing to create from, which matches the standard many2one autocomplete that only offers creation once text is entered.

Steps to reproduce:
1. Open any record with a chatter
2. Click "Send message"
3. In the recipients field type a character then delete it, leaving the field empty with the dropdown still open
4. Click the "Create" option
5. On the "What's the email address of Unnamed?" popover, click Discard

=> A blank "Unnamed" contact is created, and repeating the steps creates more

Ticket [link](https://www.odoo.com/odoo/action-4043/5942428)
opw-5942428


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

Forward-Port-Of: odoo/odoo#250973