The Knowledge article tree panel has been optimized to load articles, favorites, and access information in fewer steps. This should make navigating large Knowledge workspaces faster and smoother for users, especially when opening the side panel or the Knowledge home page.

This is done through successive commits.

The first one introduces a query counter test and then successive other commits
each improve this query counter up until the last one.

The various performances improvements include:
- Fetching all children articles that are going to be displayed all at once
- Batch compute user write access for the tree panel 
- Introduce '_parent_store' and 'parent_path' to speed up hierarchy operators
- Store the article active status on linked favorites
- Avoid checking root articles ACLs twice
- Avoid computing ACLs of the active article twice
- Avoid fetching favorited articles separately

This is best read by going through commits one by one instead of the full diff.
See underlying commits for details.

Task-2791000

Channel conversations now better distinguish regular messages from notifications. This makes discussions easier to read and helps users understand whether an item is part of the conversation or an informational update.

part of task-2918956

Community: https://github.com/odoo/odoo/pull/98262

Studio approval rules can now assign a responsible person who is automatically notified through a next activity when approval is needed. This makes pending approvals easier to track and act on, while keeping activities synchronized when approvals are granted, refused, or completed.

Before this PR, it was impractical for a "manager" to know what
approval flows were waiting for them, leaving users to manually contact
their manager on a record asking for approval of the action. This made
the feature less useful in general.

This commit introduces the notion of a "responsible" on an approval rule
that will be notified that an approval is waiting for action via a next
activity that is "linked" to the approval (so granting or refusing the
approval will automatically remove the activity, and marking the
activity as done will automatically approve the action if it hasn't
been approved or rejected already).

To keep a clean link between approval rules, records and next activities
that pertain to them, a new model 'studio.approval.request' is
introduced which models such a link (indeed, since the rule has no entry
yet, there was no clean model on which to set this link and adding a
field on activities for that was not a good idea, as it would have too
wide an impact).

Task-2895596

(also fixed a display bug)

The Knowledge article form view and related tools have been rebuilt with a newer interface framework. This should make editing articles, moving content, and managing permissions more consistent and easier to maintain, while preserving the existing business workflow.

PURPOSE

Rewrite the form view and associated widgets using OWL.

SPECS

The following components have been re-written using OWL:
- Knowledge Form View (+ Renderer + Controller)
- The various Dialogs (MoveArticleDialog, ...)
- The permission panel

Task-2942515

Corrects how Indian GSTR-1 and GSTR-3B reports calculate and display tax base values. This ensures nil-rated values appear correctly in GSTR-1 and prevents GSTR-3B from failing to open when it relies on those tax base calculations.

In GSTR-1 and GSTR-3B report if we domain_formula then label is balance but we have lable tax_base

So GSTR-1 nill rated not show value and GSTR-3B is not open because tax_base is use in aggregation formula

The Project and Field Service apps have been updated to use Odoo’s newer interface framework, making screens such as task views, project sharing, guided tours, and right-side panels more consistent and maintainable. This is mainly an internal modernization that should preserve existing workflows while improving the foundation for future enhancements.