Mesh Provisioning Service and Mesh Proxy Service exist at the same time.

[Jackistang]

Describe the bug
Mesh PB-GATT Provisioning fail with nRF Mesh Android app. Mesh Provisioning Service and Mesh Proxy Service exist at the same time.

To Reproduce
Steps to reproduce the behavior:

1. Run example 'mesh_node_demo' in posix-h4-zephyr environment.
2. Open nRF Mesh Android app and click "+ ADD NODE" to scan unprovisioned proxy device.
3. Click "Unknown Device" to connect device.
4. Click "IDENTIFY" to start provisioning device.
5. Then it is no response.

Expected behavior
According to Mesh Specification 1.0.1, Provisioner send Provisioning PDU to Device shall use Mesh Provisioning Data In characteristic. But in this situation, the Provisioning PDU - Provisioning Invite PDU is sent to Mesh Proxy Data In characteristic. So it's no response.

HCI Packet Logs
hci_dump.zip

Environment:

• Current BTstack branch: master
• Bluetooth Controller: Zephyr Controller
• Remote device: vivo X20A with Android 8.1.0

Additional context

1. In Zephyr Mesh demo, it only expose Mesh Provisioning Service when device is not provisioned.
2. In Mesh Specification 1.0.1 - Page 271, it's said that:

A device may support the Mesh Provisioning Service or the Mesh Proxy Service or both. If both are
supported, only one of these services shall be exposed in the GATT database at a time.