Condition-checking rules should check array callbacks

[ark120202]

To make iteration methods be more similar to regular conditions their return types were changed to unknown (see microsoft/TypeScript#7779 and microsoft/TypeScript#31076). Rules that check conditions (strict-boolean-expressions, no-unnecessary-condition and no-misused-promises) can be quite useful to make make it safer

[tadhgmister]

@ark120202 because the pull request didn't have the "Fixes" directive this wasn't automatically closed, would you mind closing it for house keeping purposes?

[ark120202]

It doesn't sound like it was completely resolved. Only no-unnecessary-condition appears to check it, but there are also strict-boolean-expressions and no-misused-promises (and maybe more rules I could've been missed)

[tadhgmister]

right sorry, was focused on the pull request I see now you mention those rules in your initial comment. I have already advocated for this in strict-boolean-expression.

Not sure if this feels right to put in no-misused-promises since it seems pretty specific and already checked via no-unnecessary-condition, like passing a promise to console.log isn't labeled as a problem and there isn't much we can do to check all cases where it is misuse.