Allow ignore non-existing field rule

Summary Currently on attempt fetch fields, that do not exist in the collection, we receive an error This feature was introduced in [v11.0.0]( However, it can be very useful to ignore this validation rule and return items without this field (like it was previously), for example, for M2A relations. Currently, if we want to fetch a limited subset of fields from M2A relational the only way is by using * or fetch IDs, and then making separate queries for each collection Also, it may be useful to simplify some front-end code, because sometimes developers make generalized fetch functions for several kinds of content, but with this validation rule they can't use this approach Basic Example Imagine that Menu is M2A field in the GlobalSettings model, it can contain Articles and Static pages Static pages don't have an author field, but Articles can to mark that may not exist in the model we prefix it with ? to suppress validation Motivation Without this feature in the…