Bug: Unable to delete User (with Improperly connected FirewallRule)

[melonrush13]

Describe the bug
When we create an AzureSqlUser with a bad Firewall Rule (which doesn't have access to the server), we are unable to delete the AzureSqlUser. The reconciler throws a zaperr, and the delete never finishes.

To Reproduce
Steps to reproduce the behavior:
Create an azure sql server
Create an azure sql database
Create an azure sql firewallrule with the following:

  startipaddress: 0.0.0.0
  endipaddress: 0.0.0.0

Create an azure sql user
Note: AzureSql User will NOT be able to create. We will get the following message in status:

Login error: mssql: Cannot open server 'sqlservermeltest' requested by the login. Client with IP address '73.181.19.189' is not allowed to access the server.  To enable access, use the Windows Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.

Delete the azuresql user
Will get the following zap err

}
2020-05-28T16:13:33.300-0600	ERROR	controller-runtime.controller	Reconciler error	{"controller": "azuresqluser", "request": "default/sqluser-samplemel", "error": "1 error occurred:\n\t* Login error: mssql: Cannot open server 'sqlservermeltest' requested by the login. Client with IP address '73.181.19.189' is not allowed to access the server.  To enable access, use the Windows Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.\n\n"}
github.com/go-logr/zapr.(*zapLogger).Error
	/Users/melanierush/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/Users/melanierush/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:258
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/Users/melanierush/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/Users/melanierush/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/Users/melanierush/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/Users/melanierush/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
	/Users/melanierush/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88

The azuresqluser is never able to delete.

Expected behavior
We should be able to delete an azuresqluser if it is created with a FirewallRule which doesn't have access to the server.

Fix bug for the following operators

• AzureSqlUser
• PostgreSqlUser
• MySqlUser

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[buhongw7583c]

Another edge scenario to be checked as well:
in mysqluser and postgresqluser, not define the username and create the user, then delete. The created user in service operator could be deleted but not in the database.

Check if the azuresqluser has the same issue as well.