scylladbcloud_vpc_peering should allow waiting for deletion #198
Description
Today, we had to replace one of our scylladbcloud_vpc_peering resources and add a new subnet range to it. When scylladbcloud_vpc_peering is removed, it exists immediately with a success (while in the management portal I can see it takes a few minutes to delete it), which leads to the create step failing. I the module needs to wait for the status to finalize or at least do it using a feature flag like google provider does.