This fix ensures customer website tags wrap and display properly instead of appearing cramped on a single line. It improves the readability and presentation of customer reference pages for website visitors.

Description of the issue/feature this PR addresses:

**Description:**
> - When we open the 'Customers' menu on the website, the 'tags' are displayed in a single line

**Steps:**

> - Install the "website_customer" module.
> - Create a "Website Tag" from the Contacts app-> Configurations.
> - Add the tag to any partner's "Website Tags" field (inside the "Sales & Purchase" page).
> - Go to the website and open the "Customers" menu(from url).

Current behavior before PR:

    Before Fix:
![Our-References-My-Website](https://github.com/user-attachments/assets/9d5bc1ac-d407-4225-abd0-5f5edf5d6fa8)

    After Fix:
![Our-References-My-Website(1)](https://github.com/user-attachments/assets/d9876e8a-ef52-44d0-8204-34b3325c1f36)

Desired behavior after PR is merged:

    - All Tags are appropriately shown after my fix
    - The issue comes in version 17.0, 18.0, saas~18.1, and saas~18.2

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

Pausing and resuming a subscription no longer recalculates discounts on one-time products. This prevents unexpected pricing changes and keeps customer orders consistent through subscription changes.

Discounts on non recurring products were being recomputed every time the subscription was paused and resumed. Added a protecting similar to action_confirm in order to prevent this behavior.

opw-4440500

This fix prevents an error when users add a depreciation entry to an asset that is already running. It helps accounting teams update asset depreciation schedules without interruptions or traceback messages.

After commit 6d9013f6a106d3c69eb0103504b4cae0befe05e6 it is possible to add a depreciation move on a running asset
However, the attempt terminate with a traceback error

opw-4655999

Currently ssl certificates are only generated on odoo.com based on db_uuid and enterprise_code. Since we won't be needing enterprise_code anymore we adapt our code to still recover the ssl certificate and be able to recover and log the new 'error' values sent by odoo.com task-4585446 Related PR: https://github.com/odoo/internal/pull/3425 Forward-Port-Of: odoo/odoo#203328

Currently ssl certificates are only generated on odoo.com based on db_uuid and enterprise_code. Since we won't be needing enterprise_code anymore we adapt our code to still recover the ssl certificate and be able to recover and log the new 'error' values sent by odoo.com

task-4585446

Related PR: https://github.com/odoo/internal/pull/3425

Forward-Port-Of: odoo/odoo#203328