Original PR description

The idea behind this matching is that invoices emitted by the same supplier will often look very much alike and thus share the same layout.

Using the detected layout to identify the customer of a customer invoice doesn't make sense since the layout only identifies the supplier of the invoice.
This feature should only be used on vendor bills.

Forward-Port-Of: odoo/enterprise#58312
Forward-Port-Of: odoo/enterprise#58294

Original PR description

**Current behavior before this PR:**
- Create 1 article that has an embedded kanban and 1 article inside a
   kanban(both articles are published). Now if the user opens this article
   from another user - member/portal, the user gets an error like
   'Something went wrong'.
- When an article has no members, the separator appears under the Shareable
   URLs section in the Share Wizard.

**Reason:**
- Access to the Kanban stage was only for the user who had access to that article,
   there was no condition that the stage was shown to the member/portal user if
   the article was published and the article was an item article.
- There was no condition for not showing a separator when that article had no
   members.

**Desired behavior after this PR:**
- Kanban will appear properly with read access to the portal if the article is published.
- If there is no member then the separator will not appear.

**Task**-3486083

Forward-Port-Of: odoo/enterprise#56230