wait for IP Reservations to reach the desired state

[displague]

This PR adds various features to metal_reserved_ip_block:

• Adds custom_data (a string of JSON. This enables the use of arbitrary scalar, list, and map types, as supported by the API. This is defaulted to the API default of "{}".
• Allows for tags, description, and custom_data to be updated
• Adds wait_for_state (defaults to created)
• The default behavior is now to wait for the IP Address reservation to be usable (guaranteeing an IP Address) before exiting the create call. A number of users have been snagged by this resource releasing after creating the reservation request without having an IP address fully reserved. Those users will now get a 10m timeout (default, configurable with timeouts) unless they set wait_for_state="pending"

Fixes #135

[codecov-commenter]

Codecov Report

Merging #209 (516cc6d) into main (795b495) will decrease coverage by 0.15%. The diff coverage is 59.18%.

@@            Coverage Diff             @@
##             main     #209      +/-   ##
==========================================
- Coverage   72.74%   72.59%   -0.16%     
==========================================
  Files          48       48              
  Lines        6223     6302      +79     
==========================================
+ Hits         4527     4575      +48     
- Misses       1494     1521      +27     
- Partials      202      206       +4     

Impacted Files	Coverage Δ
metal/resource_metal_reserved_ip_block.go	79.26% <59.18%> (-7.92%)	:arrow_down:
metal/resource_metal_device.go	67.53% <0.00%> (+0.71%)	:arrow_up:
metal/errors.go	71.55% <0.00%> (+3.66%)	:arrow_up:

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 795b495...516cc6d. Read the comment docs.