Redundant query on public / embedded question page with default filters

[kulyk]

When opening a public question page that has filters with default values, the app performs two queries instead of one. It's happening because of a current filter values lifecycle. The first query is done without any filters, then filters receive default values, and another request is made. Moreover, it slows down the time until people can see the relevant results.

A possible solution would be to move the logic retrieving/syncing filter default values to the upper level (e.g. PublicQuestion), so the initial query contains default filter parameters. It's currently done by syncQueryParamsWithURL at Parameters

More details here: #17034

Query and parameters lifecycle

From #17034

1. You open a URL like /public/question/:guid. There are no query parameters that are usually in sync with filters. So when the page mounts
2. PublicQuestion mounts
3. The query run is triggered inside UNSAFE_componentWillMount without parameters
4. PublicQuestion renders EmbedFrame, EmbedFrame renders Parameters
5. Parameters start syncing parameters with query parameters. At the end, it should take parameters' default values and append them to the URL as query parameters
6. Parameters trigger the setParameterValue call, so the URL can be updated and we can run the query. setParameterQuery triggers a new query run, now with default parameters applied
7. The trick is steps 3-6 happen simultaneously, and sometimes (however I can reproduce that every time), the result without filters is applied later, and you can see an error