azurerm_app_service ip_restriction - add default for priority

[aqche]

Fixes: #6876

As noted in the issue, an apply will fail with the Priority must be specified in an all or nothing manner error if multiple ip restrictions are created and some have priority specified while others do not. This PR addresses that error by setting a default priority value of 65000 (this is what Azure defaults to) instead of trying to compute the value.

=== RUN   TestAccAzureRMAppService_completeIpRestriction
=== PAUSE TestAccAzureRMAppService_completeIpRestriction
=== CONT  TestAccAzureRMAppService_completeIpRestriction
--- PASS: TestAccAzureRMAppService_completeIpRestriction (196.92s)
PASS
ok      github.com/terraform-providers/terraform-provider-azurerm/azurerm/internal/services/web/tests   196.940s

[jackofallops]

Thanks @aqche
This LGTM 👍 - Apologies for missing this behaviour in the review of the previous PR!

[ghost]

This has been released in version 2.13.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.13.0"
}
# ... other configuration ...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!