This update resolves an error preventing customers from successfully connecting or refreshing their Shopee accounts through the Odoo module. The fix corrects a technical issue within the module's code that was causing an error during the authorization process. New automated tests have been added to ensure this functionality remains stable.

Currently, customers report errors when connecting or refreshing a
Shopee account through the `sale_shopee` module.

**Steps to reproduce:**
- Install and configure the `sale_shopee` module
- Attempt to connect a Shopee account via the onboarding flow
- Complete the authorization process

**Observed behavior:**
An error is raised during the authorization callback, preventing the
Shopee account from being connected or refreshed.

**Root cause:**
In `onboarding.py`, the `shopee_return_from_authorization` controller
incorrectly uses `utils.with_context(authorization_code=code)`. Since
`utils` is an imported Python module, calling `with_context` on it
attempts to set the context on the module itself rather than on a
model instance, which raises an error.

**Solution:**
Move the `with_context` call from the `utils` module to the `temp_shop`
record, which is the appropriate model instance that needs the context.

Additionally, this commit adds regression tests for the controller to
prevent future regressions, as this functionality was previously
untested.

opw-6092524

Forward-Port-Of: odoo/enterprise#113081

This update resolves a crash that occurred when users double-clicked 'Add Custom Field' within a list view's optional fields dropdown in Odoo Studio. The fix ensures Studio isn't opened multiple times simultaneously, preventing the instability. This improves the user experience and reliability of Studio.

On a list view, open the optional fields dropdown. Click twice on "Add Custom Field"

Before this commit there was a crash, because opening studio while it is already opening was not protected.

After this commit, there is no crash.

Forward-Port-Of: odoo/enterprise#113299

This update corrects a bug where ticket submissions with emails using different capitalization would incorrectly create a new partner record. Now, the system correctly identifies and uses the submitted email address to create a ticket without generating a new partner, ensuring accurate ticket assignment and data management.

**Steps to reproduce**
- Create a first partner (name: "Partner", email: "partner@mail.com", phone: "123").
- Go to the website form of a helpdesk team, and submit a ticket using "Partner@mail.com" as email (notice the different capitalization) and "456" as phone number.

Behavior without this fix: a new partner is created, but the ticket is assigned to the orignal partner ("partner@mail.com") and its phone number is updated.

Behavior after this fix: no partner is created.

**Causes**
- the partner search was case sensitive
- the created partner was not used as the `partner_id` of the ticket as it was added to the params but needs to be in the kwargs passed to `handle_website_form` in order to be found used by `extract_data`. The original partner was found in `_find_or_create_partner` by the call to
`_mail_find_partner_from_emails` (case-insensitive)

Note: this commit also ensures consistency between the partner's company and the ticket's company (same as in `_find_or_create_partner` of `helpdesk.ticket`).
Also, avoid allowing modifying existing partner's phone via this form.

opw-5914064

Forward-Port-Of: odoo/enterprise#109393

Users can now consistently maintain their search filters within the Manufacturing Production Planning (MPS) view. Previously, returning to the MPS view after navigating away would clear the applied filters. This fix ensures the system remembers and applies the user's search criteria, improving workflow efficiency.

Issue:
In the MPS view, when the user sets a search filter, navigates away and then returns via the breadcrumb, the search filters that were applied are gone.

This happened because the MPS client action was not passing `globalState` to the `WithSearch` component.

Fix by passing `globalState` in `withSearchProps`.

task-5368078

Forward-Port-Of: odoo/enterprise#113183
Forward-Port-Of: odoo/enterprise#113125

This update fixes an issue where appointment booking descriptions were displayed in the user's language instead of the website's language (French). The change ensures that booking details are shown in the correct website language, regardless of the user's language settings, improving the user experience and consistency across the Odoo website.

When booking an appointment, the cart shows the date/time in the partner's language instead of the website's language. `_prepare_order_line_values` uses `self.partner_id.lang`, ignoring the website language and using the user's language instead.

Steps to reproduce:
1. Have a website language different than the user's language
2. Go to the website appointment page
3. Book an appointment
4. Check the booking

For this case:
- Website language: French
- User language: English

=> You will find,  "xxx at xx:xx to yyy at yy:yy" instead of  "xxx à xx:xx au yyy à yy:yy"

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

Forward-Port-Of: odoo/enterprise#113208
Forward-Port-Of: odoo/enterprise#107698

This update prevents subscriptions from being automatically reopened after manual closure by a salesperson. Previously, approvals or payments could trigger reopening, leading to inconsistencies. This change ensures subscriptions remain closed as intended, streamlining the subscription management process.

Before this commit, when a subscription was closed manually by the salesperson, it could be reopened when a transaction was approved or an invoice paid. It could cause issue. In this case, we should not reopen automatically.

task-5900481

Forward-Port-Of: odoo/enterprise#106487

This update fixes an issue where overridden group names within the accounting module weren't being properly translated into the Odoo localization files (POT). The fix ensures that translated names are exported correctly, preventing inconsistencies between the English source strings and the translated versions. This maintains accurate translations across the system.

The `account_accountant` module overrides the English name of several `res.groups` records owned by `account`. Without `account_accountant`-scoped XMLIDs for those records, the overridden names are never exported into this module's POT file. At runtime, `account`'s translations are loaded instead, which no longer match the overridden English source strings.

We fix this by registering additional XMLIDs under `account_accountant` so the overridden names get translated independently.

Forward-Port-Of: odoo/enterprise#113470
Forward-Port-Of: odoo/enterprise#112898

This update fixes a previous issue where quick checkout was disabled for event and appointment sales. We've refined the process to automatically enable quick checkout for these events, recognizing that billing addresses are typically tied to the event location rather than the customer. A system parameter allows businesses to retain full billing address details if needed.

Forward-Port-Of: odoo/enterprise#113575