Existing parties that are synced to the Wallet Gateway will have the currently connected networkId attached.
If the user switches to another network which points to the same participant (or possibly different participant with the same party hosted [multi hosting of parties]), then the sync service attempts to create a wallet for the same party, which is correct, but fails with a unique constraint on the partyId.

We should therefore consider spanning the unique constraint across (partyId, networkId).

Before doing so, we need to uncover possible unwanted side effects this change might have.