[BUG] No validation of reserved_ipv4 on civo_instance resource

[fernando-villalba]

Description

Using a completely wrong reserved_ipv4 field causes terraform to keep trying to provision this resource for two minutes rather than failing straight away:

resource "civo_instance" "foo" {
    hostname = "amazingthingy20"
    tags = ["python", "nginx"]
    notes = "This is a test-issue"
    size = "g3.xsmall"
    region = "LON1"
    reserved_ipv4 = "fsdfsdfsdfsdfsd" # This field is wrong
    firewall_id = "default-default"
    disk_image = "debian-11"
}

This should fail straight away as it does on the API, CLI, etc. Not keep retrying

Acceptance Criteria

• Have this resource fail straight away when entering the wrong value.

This ticket should be used as a reference for a bigger piece of work revamping the way we handle errors in terraform. The default behaviour with our provider seems to be to keep trying and it does NOT return the error the API gives, which is a problem.

We need to go through the entire provider and change the behaviour for everything not by writing error messages in terraform provider, but returning errors from the API