Fix to consider that a custom hostname fallback origin can move to active during a retry

[marc-barry]

We have been trying to use the new custom hostname fallback origin creation functionality of the provider and consistently hit the following error:

Error: expected custom hostname fallback to be created but was active

I traced the issue to the following condition:

if fallbackHostname.Status != "pending_deployment" {	
    return resource.RetryableError(fmt.Errorf("expected custom hostname fallback to be created but was %s", fallbackHostname.Status))
}

The issue is that our custom hostname fallback origins from the https://api.cloudflare.com/#custom-hostname-fallback-origin-for-a-zone-properties API calls end up in the active state during the retry period. The retry logic didn't account for that state change and thus our custom domain fallback origin creation fails.

[jacobbednarz]

Thanks for this one @marc-barry! Are you able to remove go.sum and we can get this one merged?

[marc-barry]

Thanks for this one @marc-barry! Are you able to remove go.sum and we can get this one merged?

@jacobbednarz I reverted the go.sum back to its original state in def1b37.