Find "changed" not only in first "when" condition

[klaus-tux]

Prior to this change, the rule no_handler did not find the string "changed" if it was in the second when condition or any later when condition:

- name: This should be a handler 1
  ansible.builtin.debug:
    msg: why isn't this a handler
  when:
    - result.changed # ansible-lint finds this
    - second_condition

- name: This should be a handler 2
  ansible.builtin.debug:
    msg: why isn't this a handler
  when:
    - first_condition
    - result.changed # ansible-lint misses this

This change fixes the implementation so that it finds the second case as well.

[StopMotionCuber]

I just stumbled upon that as this PR broke our CI on ansible-lint and raise that something into this direction was discussed on #1632

While I agree that it should be consistent (either match on any when condition or none at all if there is more than 1 line available), I'm not sure whether these cases with multiple conditions should be linted. Internally on our team, we added a noqa on the violated tasks

[klaus-tux]

I was not aware of #1632 when I created the PR. I just spotted an inconsistency and fixed it.

@ssbarnea What is the desired behaviour here? Should we disable the check for complex conditions or should we leave the implementation as it is?