Better req function exception messages

[nicopop]

while testing for my YamlCompare req rule (ill do another pr soon)
I noticed that whenever a requirement function cause an exception its not that clear where/what function caused said error unless actively debugging (which is not something most of the devs will do)
to do this I added a try except with a custom message that tell exactly in what area the function was called.

before this it would jump to the green part of the image
I also changed the recusion test from >= to > so it make more sense with existing error message

I know line 143 of rules.py look weird but in fstring the way to escape {} is to double them
like so "{{{func_name}({item[1]})}}" become this in output: {func_name(item[1])}