Implement QueryData for &Archetype and EntityLocation

[james7132]

Objective

Fixes #12392, fixes #12393, and fixes #11387. Implement QueryData for Archetype and EntityLocation.

Solution

Add impls for both of the types.

---

Changelog

Added: &Archetype now implements QueryData
Added: EntityLocation now implements QueryData

[alice-i-cecile]

@urben1680 feel free to live a review here if you're comfortable.

[urben1680]

I would like the two types being mentioned in the Query::transmute_lens docs that these can be added and removed as wished, just as Entity.

Might switch it to dense to not break existing dense queries.

Would the implementation as it is right now here, besides the IS_DENSE value, not be what a dense WorldQuery look like? Why was false picked?

[james7132]

Would the implementation as it is right now here, besides the IS_DENSE value, not be what a dense WorldQuery look like? Why was false picked?

set_archetype is never called on dense fetches, as it's table oriented instead. The Option in the fetch would always be None, and hence the debug_checked_unwrap would always panic or become undefined behavior.

If we were instead to take the entity, look up its location, then use its location to look up its archetype, it would work with both, but that would likely be slower in isolation than just returning back the assigned archetype.

I'm leaning towards making it dense, as making it force archetypal iteration will likely be slower in any compound query.