Context Navigation

Changes between Initial Version and Version 1 of Ticket #32801

initial	v1
100	100	While implementing this workaround, I found a few issues:
101	101	1. I was unable to find a good way to have the query layer automatically resolve a reference to an annotation defined in a subquery without redefining it. While aggregated queries technically seem to have support for this, it appears they "lift" the annotation into the outer query instead of referring to the annotation within the subquery. This distinction is important for `jsonb_array_elements`.
102		2. Because of #1, I had to annotate the outer query and then find a way to trick the query later to use a field name that would resolve when executed against the DB.
	102	2. Because of (1), I had to annotate the outer query and then find a way to trick the query later to use a field name that would resolve when executed against the DB.
103	103	3. While the query layer seems to handle renaming aliases in subqueries for aggregate queries, I had to manually change the outer query table alias to properly refer to the subquery fields.
104	104