Consider the case that "Predict vendor bill product" is activated in the settings and we upload / import a vendor bill with a single line. In case the product on the line could not be determined by the import function it is predicted afterwards (since the setting is enabled). But changing the product triggers i.e. a recompute of the unit price (`price_unit`) and taxes (`tax_ids`) based on the new product information. This is not what we want since the aforementioned values should be det

Consider the case that "Predict vendor bill product" is activated in
the settings and we upload / import a vendor bill with a single line.
In case the product on the line could not be determined by the import
function it is predicted afterwards (since the setting is enabled).

But changing the product triggers i.e. a recompute of the unit price
(`price_unit`) and taxes (`tax_ids`) based on the new product information.
This is not what we want since the aforementioned values should be
determined by the import even in case the product is not found.

After this commit we protect the unit price and taxes fields
during any (product) prediction in case they are set.
(We do update the unit price and tax if it is 0 or there are no taxes.)

Reproduce
1. Activate "Predict vendor bill product" in the settings
2. Create Customer OpsWay
   * country = Poland
   * VAT = PL8992922295
3. Create 3 Vendor Bills manually
   * date in the past
   * customer = OpsWay
   * single invoice line: with product "Commissions"
   * Confirm
4. Import the PDF attached on the task in Vendor Bills.
   * It has a single line with quantity 1 and unit price 1,322.40
5. A bill with a single line is created:
   product = "Commissions"
   unit price = 0.0
   total = 0

task-4279931

Forward-Port-Of: odoo/enterprise#73191
Forward-Port-Of: odoo/enterprise#72625

Commit [1] optimized the `has_group` util to avoid a RPC for information that is already in the session_info. The problem is that it supposed that this information would always be available in there, which was already not the case for the frontend `session_info` when this was done. This commit simply makes the util not cache a value if there was actually no found value, and thus let the util falls back to making a RPC if needed. Note that in 18.0, the user service is actually not a service

This update addresses a user experience issue by displaying an error modal when attempting to access deleted tweets or posts. Due to the complex, network-specific requirements for handling deleted posts, this change was implemented in the stable version to avoid disrupting future development. This ensures a consistent user experience for accessing social media content.

This commit adds a new error modal when you clicking on deleted tweets and
posts.
It was decided to do so in stable as properly handling deleted posts requires
a more consistent approach for each social network.
This work should instead be done in later versions as such work will require a
lot of changes. Which is against our stable version policy.

task-3999571

Forward-Port-Of: odoo/enterprise#72871
Forward-Port-Of: odoo/enterprise#69168