Multiple issues with Bicep deployment

This is a meta-issue to highlight the many problems with deploying a Static Web App resource with Bicep or ARM templates.

1. https://github.com/Azure/static-web-apps/issues/516 This is still a problem even though the issue was closed. Take a look at [Johnny Reilly's blog post](https://blog.johnnyreilly.com/2021/08/15/bicep-azure-static-web-apps-azure-devops/) for the level of hackery that is currently required to get this to work, e.g. disconnecting the Static Web App before running the Bicep deployment.
- See also https://github.com/Azure/static-web-apps/issues/575, https://github.com/Azure/static-web-apps/issues/495.
2. https://github.com/Azure/static-web-apps/issues/576 Deploying a `Microsoft.Web/staticSites/userProvidedFunctionApps` resource is not idempotent. The second time you attempt the deployment, it will fail with "Cannot register a function app with a preexisting Azure Static Web Apps configuration without setting the isForced flag to true."
3. https://github.com/Azure/static-web-apps/issues/477 A Bicep deployment of a Static Web App will fail with a misleading error message if the `properties` key is omitted. Omitting the `properties` key should be equivalent to `properties: {}`. This is how it works for every other Azure resource as far as I know.

I have not personally experienced the following issues, but I figured I would mention them here.

4. https://github.com/Azure/static-web-apps/issues/577
5. https://github.com/Azure/static-web-apps/issues/571