fix(vue-instantsearch): properly add noRefinement class on <ais-refinement-list>

[sarahdayan]

Summary

When the is searchable and a user searches for a facet value that doesn't exist, the root should have the class .ais-RefinementList--noRefinement. This was however not the case because we were relying on canRefine which remains true as long as the last search contains search results.

Now we're relying on the items returned from SFFV.

In the future, we may want to reconsider what canRefine means in the context of connectRefinementList, as the source of refinements comes from two places (main search and SFFV), but this would be breaking right now so we can keep it for later.

Note

This change doesn't update tests, because existing ones weren't testing this use case. This will be touched on in #6090.

[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 df173a4:

Sandbox	Source
react-instantsearch-app	Configuration
example-react-instantsearch-default-theme	Configuration
example-react-instantsearch-next-app-dir-example	Configuration
example-vue-instantsearch-default-theme	Configuration

[Haroenv]

surprised there are no tests on this in vue. Did you also leave a comment on the InstantSearch.js connector that we want to change the meaning of canRefine in the next major?

[sarahdayan]

Did you also leave a comment on the InstantSearch.js connector that we want to change the meaning of canRefine in the next major?

@Haroenv Just did in df173a4 so we don't forget about it.