Release v22.112.1

Changed

• useQuery: changing an optional argument now fetches again, as changing a required argument already did. (#3312)

Fixed

• useQuery: when two components read the same query with the same arguments, the one whose request was cancelled by the other now receives the result instead of staying "not ready" with no data. A failed request settles both components as failed, and neither keeps reporting that it is performing. useQueryWithPaging gets the same fix. (#3312)
• useQuery: a component whose arguments, paging or sorting change no longer shares a query instance, or a cached result, with components that use the previous values, so a request for new arguments can no longer cancel or overwrite another component's request. (#3312)