Remove jinja2 templating from conditionals in keycloak integration tests (#9726)

[armkeh]

SUMMARY

Fix warnings and failures in keycloak module integration tests caused by use of jinja2 templating in conditionals.

Fixes #9726.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

keycloak_role

ADDITIONAL INFORMATION

To run the test, first start Keycloak:

docker run --rm --name mykeycloak -p 8080:8080 -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=password quay.io/keycloak/keycloak:latest start-dev --http-relative-path /auth

Then run one of the affected integration tests, e.g.,

ansible-test integration keycloak_role --allow-unsupported -vvv

Sample of existing test behaviour (in this case, causing a failure in the keycloak_role module tests):

# ...
TASK [keycloak_role : Assert client role created] ******************************
task path: /home/armkeh/projects/ansible_collections/community/general/tests/output/.tmp/integration/keycloak_role-752i69kl-ÅÑŚÌβŁÈ/tests/integration/targets/keycloak_role/tasks/main.yml:154
[WARNING]: conditional statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found: result.end_state.name == "{{ role }}"
[WARNING]: conditional statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found: result.end_state.containerId == "{{
client.end_state.id }}"
fatal: [testhost]: FAILED! => {
    "msg": "The conditional check 'result.end_state.containerId == \"{{ client.end_state.id }}\"' failed. The error was: Conditional is marked as unsafe, and cannot be evaluated."
}

PLAY RECAP *********************************************************************
testhost                   : ok=20   changed=6    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0  
# ...

[armkeh]

Marked as draft for the moment while I check if other modules have the same problem. From my previous checks, I don't think any other module's tests are failing due to this, but I didn't check for warnings yet.