Context Navigation

Changes between Version 2 and Version 3 of Ticket #34871, comment 10

-              v2
+              v3
 All `UnresolvedLookup` would do in its `resolve_expressions` is [https://github.com/django/django/blob/f835787f714cf000603516188b5516f87aa348b1/django/db/models/sql/query.py#L1496-L1598 what can be found in the trailing part] of `Query.build_filter` today that calls `solve_lookup_type`, `resolve_lookup_value`, and `build_lookup` but it would behave like a normal expression and avoids all the hacks we have in place today that special case `Q` objects.
 Until work towards ^^ can be made the best solution here is to use lookups directly
+Until work towards ^^ can be made the best solution here is to use lookups directly to palliate the lack of support for unresolved lookups introspection
 {{{#!python
 …
         name="unique_active_email",
+    )
+)
 }}}