feat(dynamicWidgets): request wildcard facets by default

[Haroenv]

Summary

make sure only one network request happens on mount of dynamic widgets, and no extra request when the requested widgets change

Result

use algolia/algoliasearch-helper-js#874 if the wildcard is requested

[seafoox]

Can you please provide an example for each of the case

• Default behaviour with * used
• Sequential behaviour where we wait the response from the first query in order to know what facet to retrieve value for.

I think understand that people would need to use wildcardFacets=true|false, but would like to confirm my understanding.

Thanks,

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 9fae8cb:

Sandbox	Source
InstantSearch.js	Configuration

[Haroenv]

different scenarios:

• status quo: two network requests on mount, no *
• facets * without updating helper: two network requests on mount, both including *
• facets * with helper features: one network request on mount, including only *

[francoischalifour]

Explaining another user-land solution so we can track it and document it:

If users have too many facets in their index and that wildcardFacets is too expensive (in terms of parsing the API response), they can mount a configure widget to declare the facets required at initial load.

(In any way, none of these solutions works with an initial UI state.)

[Haroenv]

this test fails now as the second request also has maxValuesPerFacet 🤔