Root cause:
Since https://github.com/odoo/odoo/commit/f5cf856 the table of contents uses the scrollTo helper from web to reach the clicked heading. The helper only makes the element visible. When the heading is below the screen it is placed at the bottom border of the scrollable area, so the reader sees the heading but not the section under it. The second scrollTo call that was meant to correct this does nothing because the heading is already visible after the first scroll, so no branch of the helper runs.

Fix:
Pass isAnchor to the scrollTo call in scrollIntoView of table_of_content_manager.js. With this option the helper always places the element at the top of the scrollable area in both scroll directions, and the offset computed for sticky elements keeps working. The second scrollTo call is removed since one call is enough. This method is the one changed by the commit above and it is used by the editor and the readonly viewer, so both are fixed.

Steps to reproduce:
1. Open the Knowledge app and create an article
2. Add several headings with paragraphs between them so the article is longer than the screen
3. Type /table and insert a Table of Contents at the top of the article
4. Click an entry of the table of contents that points to a heading below the visible part of the page

=> the page scrolls so the heading is at the bottom of the page instead of the top

Ticket [link](https://www.odoo.com/odoo/project/49/tasks/6376092)

opw-6376092

Steps to reproduce:
--------------------------------------
1. Install the `mail_group` module
2. Go to Settings > Technical > Email > Alias Domains
3. Create an alias domain, for example, `localsystem.com`
4. Go to Settings > Technical > Discuss > Mail Groups
5. Open a mail group, for example, My Company News
6. Click the Emails smart button.
7. Create a new email, set the subject, author, and content, and accept the message
8. Go to Settings > Technical > Email > Emails and click Send Now if necessary
9. Inspect the Reply-To header of the received email.

Current Behavior:
--------------------------------------
The Reply-To address uses the display name of the author.
`Reply-To: 'Mitchell Admin' <newsletter@localsystem.com>`

Expected Behavior:
--------------------------------------
The Reply-To address should use the display name of the mail group.
`Reply-To: 'My Company News' <newsletter@localsystem.com>`

Issue:
---------------------------------------
When email notifications were sent from a mail group (`mail.group`), the `Reply-To` header incorrectly used the author's display name instead of the mail group's name (`self.name`)
https://github.com/odoo/odoo/blob/8990a10aa786be4c124ba3d228e7e23c50886fad/addons/mail/models/models.py#L693-L696

Solution:
---------------------------------------
1. Extracted display name logic into a separate `_notify_get_reply_to_name` method, which is overridden in `mail.group` to use the group's name as the Reply-To display name.
2. Updated `_notify_get_reply_to_batch` to browse the specific `res_id` before calling `_notify_get_reply_to_formatted_email`, since the method only needs the record being processed instead of the entire multi-record in self.
3. Ensured safe batch processing by providing a singleton record to the `mail.group` override, allowing it to safely access `self.name` without causing Expected singleton errors.

opw-6379281

Before:
--------------
<img width="930" height="354" alt="image" src="https://github.com/user-attachments/assets/ef8a297b-28c4-4601-8c5f-b69e9ed43296" />

After:
--------------
<img width="996" height="359" alt="image" src="https://github.com/user-attachments/assets/bd83a7ac-2026-4ad8-ac02-c167417fec7c" />

**Steps to reproduce:**

- Create a contact with a phone number that has 9 characters
- Setup an UPS carrier, a configuration that works is UPS Saver as Service Type and UPS Package/customer supplied as a package type
- Create a quotation, put the created contact as a client
- Try adding a shipping and getting the rates
- An User Error appears, the phone number is too short

**Why the fix:**

Before this commit, any phone number that was less than 10 characters would raise an User Error, but some countries, such as Luxembourg, use phone numbers that are nine characters long or even less.

If we check the official UPS documentation (https://developer.ups.com/tag/Shipping?loc=en_EN#operation/Shipment), we can see in the Ship_to/Phone section, that the phone number should be a number between 1 and 15, not saying it should be 10 characters or more.
<img width="495" height="473" alt="image" src="https://github.com/user-attachments/assets/fed82987-ffb8-4b84-b282-6c3d3b4f304e" />


After this commit, we adapt the way we prevent the user from inputing phone numbers to fit the official UPS documentation.

opw-6307577

Forward-Port-Of: odoo/enterprise#122831