pos*: l10n_in_pos, point_of_sale, pos_restaurant

This commit solves multiple tracebacks and bugs in the POS.

1.
    Fix traceback when deleting demo records in POS.
        When deleting some demo orders in the POS, a traceback was
        raised because the lines of the orders did not had an order
        linked to it. This was because they did not have an uuid.
        We now have default uuid values for orders, order lines and
        pos payments.

2.
    Fix customer count not update.
        When changing the customer count on an order in the POS, the
        customer count was not updated in the backend. This was because
        the customer count was not correctly updated in the frontend
        leading to a customer count of 0 in the backend.

3.
    Fix "Select table to transfer order" not visible on mobile.
        When transfering an order in mobile, the text "Select table to
        transfer order" was not visible because the text was too big.
        We now display "Transferring" when in mobile. We also stop
        showing the floating orders tab when transferring an order as it
        makes no sense to show it.

Enterprise PR: https://github.com/odoo/enterprise/pull/70357

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

Currently, multiple tracebacks occur when the user tries to access 
the asset group through the internal link from the assets and the loans form view.

To reproduce these issues:

  Traceback 1:
      1) Install Accounting
      2) Create a new loans record from Accounting/Loans
      3) Create a new asset group and open the group record through an internal link

```
ValueError: Compute method failed to assign account.asset.group(2,).count_linked_assets
```
  Traceback 2:
    1) Create a new assets record from Accounting/assets
    2) Create a new asset group and open the group record through an internal link

```
ValueError: Compute method failed to assign account.asset.group(2,).count_linked_loans
```
When a user creates an asset group record from loans, the `count_linked_asset` value is not assigned. 
Conversely, when creating a group from assets, the `count_linked_loan` field remains unassigned. 

Both of these fields are compute fields, and the compute methods have failed to assign values,
resulting in the tracebacks mentioned above.

Giving a fallback value will resolve this issue.

sentry-5967765739

### Steps to reproduce:
- Create a Helpdesk team with the options "Return" and "Repairs"
- Create a product, sell 1 unit and deliver it.
- Create a ticket for the Helpdesk Team, select the customer who bought the product > create and validate a return of the product to your warehouse through the ticket.
- Create an associated repair order and add a line for an other product in the part tabs
- Go back to the return picking

#### > the product added to the repair was also added to the return picking

### Cause of the issue:

A `default_picking_id` is added to the context of the form view of the repair order by the `_prepare_repairs_default_value` of the `action_repair_order_form` so that it prefils the form of the repair: https://github.com/odoo/enterprise/blob/e74b05fa7a777053fd0e2cd5a265de365e1e434a/helpdesk_repair/models/helpdesk_ticket.py#L36-L40 https://github.com/odoo/enterprise/blob/e74b05fa7a777053fd0e2cd5a265de365e1e434a/helpdesk_repair/models/helpdesk_ticket.py#L55-L56 However, this values stays in the context and will be added as a default value for each of the move that will be creted from this view.

### Fix:

Thanks to commit odoo/odoo@3898d61046cc0338082fdcbe0df282241372361a, we now have a default getter that can be used to associate a default picking id to the repair order when necessary without the need to put a `default_picking_id` in the context.

opw-4159779

Commit 1
========

Steps to reproduce the issue:
- add comment to a Facebook/youtube post.
- keeping the `Comments` dialog box open, try replying the same comment.
- we get a traceback.

Reason:
- due to the missing comments data structure, we get an error when trying to add the new comment.
- LOC responsible for the traceback: https://github.com/odoo/enterprise/blob/16.0/social/static/src/xml/social_templates.xml#L311

Fix:
- since the comments data structure is not returned from the post request made to post the commnet, we manually ensure it exists.

Commit 2
========

[FIX] social: fix various issues
1. social_instagram:

ISSUES:
- create a post on the instagram platform with commenting turned off.
- try commenting on it from Odoo. We get a traceback.
- also, if we delete the post from the platform and then try to comment from Odoo,
  we get a traceback.

REASON:
- there is no existing implementation to check if commenting is enabled/disabled
  on the post.

FIX:
- we now check if commenting is enabled or not while trying to add comment on the post

TECHNICAL NOTE:
- the correct way to check if commenting on a post is enabled or not is to request
  a field named `is_comment_enabled`.
- more details --- https://developers.facebook.com/docs/instagram-platform/instagram-graph-api/reference/ig-media
- but to save us from making an extra request, we simply catch the error received to
  when trying to add a comment.

================================================================================

2. social_linkedin

ISSUE:
- delete an existing post from the linkedIn platform.
- now try commenting on it from Odoo. We get a traceback.

REASON:
- The response received from the request to fetch the comments is not validated.

FIX:
- validating the response before further execution.

Task-3759530

Forward-Port-Of: odoo/enterprise#67079