Add a `Includes` query filter for working with disabling components

[alice-i-cecile]

IMO this should include an example of a Query that matches entities that are both enabled and disabled. The ones shown match only entities that are disabled.

Has matches both!

Ah right. It still feels kinda hacky though.

Originally posted by @SkiFire13 in #17768 (comment)

When working with default query filters, it's reasonably common to want to be agnostic to the presence of a given disabling component.

Currently, users can stick a Has or Option query data term in there, and get the desired behavior, but they often don't want the information contained in that term.

We should provide them with a query filter equivalent, which I think should be called Includes<C>. This filter would be absolutely useless for normal components, as it includes entities with or without C. But if we set the access up correctly, this should trick DQF into showing us the entities we want, regardless of whether or not they have C.

[Wuketuke]

Im currently trying to implement this feature, and to me Includes<T> sounds very similar to With<T>. Maybe it should be called Allows<T> to differentiate it further?

[alice-i-cecile]

Allows is a great name.