Integration tests version handling

[lgetwan]

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Previously, the version dependencies (e.g. different format in the raw_value) in the tests were handled by the task/test.yml.

What is the new behavior?

• Introduced separate variable files for each Checkmk version.
• Fixed a typo in an author's name.
• Removed the "Create rules. Oldschool." tasks, as they are already handled by the given test cases.

Other Information

When using a registered variable from a previous rule module task, please take care when using the raw_value. Ansible will interpret the value and probably change it. To restrict that, use the "string" filter like that:

- name: "{{ outer_item.version }} - {{ outer_item.edition | upper }} - Modify rules."
  rule:
    server_url: "{{ checkmk_var_server_url }}"
    site: "{{ outer_item.site }}"
    automation_user: "{{ checkmk_var_automation_user }}"
    automation_secret: "{{ checkmk_var_automation_secret }}"
    ruleset: "{{ item.content.extensions.ruleset }}"
    rule:
      rule_id: "{{ item.content.id }}"
      conditions: "{{ item.content.extensions.conditions }}"
      properties:
          comment: "{{ item.content.extensions.properties.comment | default('') }}"
          description: "New description"
      value_raw: "{{ item.content.extensions.value_raw | string }}"
    state: "present"
  loop: "{{ created_rules.results }}"

[lgetwan]

All tests successful, including the rule integration tests. :-)
@robin-checkmk: Please check and merge, if you're fine with it.

[robin-checkmk]

Love the approach! 🏇

Might be a little added effort to maintain the rules, but I think it is worth it. 👍