<!--- Verify first that your feature was not already discussed on GitHub -->
<!--- Complete *all* sections as described, this form is processed automatically -->

##### SUMMARY
<!--- Describe the new feature/improvement briefly below -->
Atm, there is no way to put the server in rescue mode

##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
hcloud_server

##### ADDITIONAL INFORMATION
<!--- Describe how the feature would be used, why it is needed and what it would solve -->
Atm, Since I can use the hetzner api, I'm using the following code to put it into rescue:
<!--- Paste example playbooks or commands between quotes below -->
```yaml
    - name: Enable rescue
      uri:
        url: "https://api.hetzner.cloud/v1/servers/{{ item }}/actions/enable_rescue"
        method: POST
        status_code: 201
        body_format: json
        body:
          type: "linux64"
          ssh_keys: [341997]
        headers:
          Content-Type: "application/json"
          Authorization: "Bearer {{ hostvars['localhost']['hetzner_api_token'] }}"
      with_items:
        - "{{ server_id }}"
```

<!--- HINT: You can also paste gist.github.com links for larger files -->

options:
    id:
        description:
            - The ID of the Hetzner Cloud server to manage.
            - Only required if no server I(name) is given
        type: int
    name:
        description:
            - The Name of the Hetzner Cloud server to manage.
            - Only required if no server I(id) is given or a server does not exists.
        type: str
    server_type:
        description:
            - The Server Type of the Hetzner Cloud server to manage.
            - Required if server does not exists.
        type: str
    ssh_keys:
        description:
            - List of SSH key names
            - The key names correspond to the SSH keys configured for your
              Hetzner Cloud account access.
        type: list
    volumes:
        description:
            - List of Volumes IDs that should be attached to the server on server creation.
        type: list
    image:
        description:
            - Image the server should be created from.
            - Required if server does not exists.