The automember_add_condition and automember_remove_condition commands
are not verifying condition keys in all cases. This is for example not
done in the removal case if a condition is not part of the automember
rule.

For consistent behaviour this needs to be done in the automember module
now. The condition keys are verified with the user and group aciattrs
returned by the API command json_metadata now.

Related: RHBZ#1976926

Instead of ignoring errors it is better that we specific evaluate
errors provided by negative tests. This patche removes the an
occurrence of 'ignore_errors: true' in ansible-freeipa tests.

    There is a new automember management module placed in the plugins folder:

        plugins/modules/ipaautomember.py

    The automember module allows to ensure presence or absence of automember rules
    and manage automember rule conditions.

    Here is the documentation for the module:

        README-automember.md

    New example playbooks have been added:

        playbooks/automember/automember-group-absent.yml
        playbooks/automember/automember-group-present.yml
        playbooks/automember/automember-hostgroup-absent.yml
        playbooks/automember/automember-hostgroup-present.yml
        playbooks/automember/automember-hostgroup-rule-absent.yml
        playbooks/automember/automember-hostgroup-rule-present.yml

    New tests for the module:

        tests/automember/test_automember.yml

The task "Verify if modification worked" failed with PR #545 because the
ipaadmin_password was missing in the task.

Test task was missing zone and entry name.

Creation of reverse zone names were not using the pre-computed array,
and creation of the 8-bit network was wrong.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For the "Duplicate names in users failure test" failed_when: not
result.failed has been added as this test needs to fail.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

Fixed also "User test cert members present again" task, it was failing
due to also having first and last parameters with action: member.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

Only renamed again may not use failed_when result.failed as the rename
can not be idempotent.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

failed_when result.failed can not be used for the unknown user test
with membermanager_user as this needs to fail.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For the duplicate names in hosts test failed_when: not result.failed has
been added as this test needs to fail.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.

For failed_when result.failed should be used to make sure that
the task fails if there was an error.