add missing features to existing resources

[ghost]

Implementing the missing features of existing resources (new actions, new attributes) in this PR.

List of requirements compiled from #30

Some server attributes have already been implemented before this PR.

(!) = Blocked by other PR

• Images have Actions
• Servers have metrics
• Servers Action add_to_placement_group
• Servers Action change_alias_ips
• Servers Action change_dns_ptr
• Servers Action remove_from_placement_group
• Server attribute backup_window
• Server attribute iso (resource type)
• Server attribute labels (currently hash)
• (!) lib: implement load balancer #55 Server attribute load_balancers (currently array) (resource type)
• Server attribute placement_group (resource type)
• Server attribute private_net (currently array) (resource type)
• Server attribute protection ({"delete"=>false, "rebuild"=>false})
• Server attribute public_net (currently hash), has sub fields that are resource types
  • primary IPs
  • floating IPs
  • firewalls (this one is a bit harder to handle as next to the ID it has the additional field status, which describes the relationship between the server and the firewall)
    • open issue: the ID is in a hash in the :id key, so the parsed firewall object also is in the :id key
• Server attribute volumes (currently list) (resource type)
• Network Action change_ip_range
• Floating IPs parameter name on create
• Floating IPs parameter name on update
• Image parameter status on get all
• Image parameter include_deprecated on get all
• Placement groups parameter label_selector on get all
• Server parameter automount on create
• Server parameter firewalls on create
• Server parameter placement_group on create
• Server parameter public_net on create
• Server parameter volumes on create
• SSH key parameter fingerprint on get all
• Volume parameter status on get all

TODO after #55 merged:

• add it_supports_search to load balancer spec
• add it_supports_search to load balancer type spec

Closes #30

[ghost]

Solved the problematic firewalls: [{ id: 12345, status: "applied" }] with a raw_data on our Future object.

Accessing the Firewall object with server.public_net[:firewalls][0][:id] # type Firewall would be weird. A user can expect to get the firewall on server.public_net[:firewalls][0]. But then we lose the applied status information.

Luckily, server.public_net[:firewalls][0] does not really hold a Firewall object, it holds a Future which transparently forwards every method to a Firewall object. I added a method raw_data to this Future, which returns the actual Hash/JSON data.

Users can now request the hidden data (e.g. applied status) like this:

# basically a Firewall object (in reality a Future, but forwards everything to Firewall)
server.public_net[:firewalls][0]

# get the { id: 12345, status: 'applied' } hash
server.public_net[:firewalls][0].raw_data

[ghost]

Since this is still an MR from my fork and tests do not run. I think all tests should be green, at least they are locally:

• bundle exec rubocop: OK
• LEGACY_TESTS=y bundle exec rspec -t '~doubles': OK
• bundle exec rspec -t doubles --order rand: OK