This change fixes an internal Point of Sale issue where receipt screen code depended on restaurant-specific functionality. The same behavior remains available through the proper existing extension, reducing runbot errors without changing the user experience.

A method declared in restaurant was used in point_of_sale module which is causing an error in runbot. This commit removes the function from point_of_sale module.

The behavior is kept via a pre-existing override.

Typing into the Google address autocomplete field now marks the record as changed, so users are prompted to save and their edits are not silently ignored. This improves reliability when entering or adjusting addresses with autocomplete.

…ing in it

Before this commit, when typing in the field, the change did not make the record dirty.

After this commit it does.

opw-4464355

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

A duplicated internal identifier in the base security rules was corrected so one rule no longer overwrites another. This helps ensure the intended access settings are applied reliably without changing day-to-day workflows.

The rule introduced shared the same xmlid as the one above, overriding the value.

This fixes internal test expectations after an upstream change altered how many database queries are expected. The change helps keep automated checks reliable without changing business workflows or user-facing behavior.

enterprise version of odoo/odoo#193052

odoo/odoo@a4a87c2 overrode an existing external id. odoo/oddo@824a641 adapted the query counts without this rule