Deployment fails when deploying Azure Data Share template for the second time

[data-share-share-storage-account](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.datashare/data-share-share-storage-account)

Not sure if this is the right place, but don't know where else to report it. Currently I am setting up a Data Share account using ARM template/bicep. This works successfully, but deploying it for the second time will result in conflicts.

### Issue Details

1. Deploy [template](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.datashare/data-share-share-storage-account)
2. Deploy same template again with same settings
3. Redeployment fails with conflicts for `Microsoft.DataShare/accounts/shares/dataSets` and `Microsoft.DataShare/accounts/shares/synchronizationSettings`


For me the philosophy of ARM templates is that they deploy a desired state. Since the infrastructure of _data sets_ and _synchronizationSettingsis_ is already there, it should recognize that and not result in a conflict. Also I am not sure about the choice to deploy the invitation via the ARM template. Everytime I deploy it, it will send an invitation mail.

### Status messages

For `Microsoft.DataShare/accounts/shares/dataSets`:
```json
{
"status": "Failed",
"error": {
"code": "5005",
"message": "DataSet name already exists in this share",
"details": []
}
}
```

For `Microsoft.DataShare/accounts/shares/synchronizationSettings`:
```json
{
"status": "Failed",
"error": {
"code": "13000",
"message": "A synchronization setting of this kind already exists",
"details": []
}
}
```

Start with quickstarts/microsoft.datashare/data-share-share-storage-account and deploy the template once, then repeat the deployment with the same settings. Inspect the failures for Microsoft.DataShare/accounts/shares/dataSets and synchronizationSettings, including status codes 5005 and 13000. Done means the redeployment behavior and the invitation behavior are resolved or clearly documented in the template issue.

Written by the indexing model from the issue text.