Enhance Error Handling of all(), any()

[coderabbitai]

An issue has been identified in the and methods within the class, where the error handling and messaging could be improved to provide more detailed information about failed conditions when no widgets fulfill the provided matcher.

This enhancement request was raised during the review of Pull Request #43 (#43), specifically in the context of a discussion on improving the method's error messaging (#43 (comment)).

The goal is to make the error messages more informative and helpful for developers by including details about the failed conditions, thereby facilitating easier debugging and a better understanding of why a test might have failed.

Requested by @passsy.