Original PR description

Before this commit, new test "Show conversations with new message in chat hub (outside of discuss app)" would non-deterministically crash with following error:

```
Failed to find 0 of ".o-mail-ChatBubble[name='Dumbledore']" (Timeout of 3 seconds). Found 1 instead.
```

This happens because the test `start()` and immediately simulate a new message from another user to show a chat bubble with badge "1". The badge is shown when this is a new message from init messaging, which doesn't necessarily mean `await start()` has messaging fully initialized. When discuss is not fully initialized, the new message post would be considered as not a new message and thus wouldn't open a chat bubble with badge.

This commit fixes the issue by using a similar pattern as many other tests to ensure discuss is fully loaded initially: have it open a conversation with at least 1 message and assert the message is visible on the UI.

Fixes https://runbot.odoo.com/runbot/build/85195954

Original PR description

* Problem: Since what has been described in https://github.com/odoo/odoo/pull/214134 and
https://thuvienphapluat.vn/chinh-sach-phap-luat-moi/vn/ho-tro-phap-luat/chinh-sach-moi/82581/tu-ngay-01-7-2025-ca-nuoc-se-khong-con-quan-huyen Vietnam no longer have district and city in city no more (Before in Vietnam we will have Thu Duc City belong to Ho Chi Minh State or Thuy Nguyen City belong to Hai Phong), Therefore we need to update Sinvoice data for this to.

* This commit remove BuyerDistrict parameter , beside using state in the district is totally wrong and for 'buyerCityName' accept city or state field because odoo user might leave the city empty and just input state

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

Forward-Port-Of: odoo/odoo#218984