fix(disjunctiveFacets): avoid escaping non-string values

[Haroenv]

This wasn't fully functioning behaviour before #889 already, as numeric values don't show as refined, even if they are (see

algoliasearch-helper-js/src/SearchParameters/RefinementList.js

Line 141 in dd375ab

var refinementValueAsString = '' + refinementValue;

where it's purposely casted to a string, but the input values aren't), but it didn't throw an error, which became the case in #889

A customer discovered this in https://algolia.atlassian.net/browse/CR-883

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

Sandbox	Source
javascript-helper-app	Configuration
InstantSearch.js	Configuration

[Haroenv]

I haven't changed the behaviour of "injected numeric facets"' isRefined, it really should be true, but that was the case before #889 already

other relevant part of the code:

algoliasearch-helper-js/src/SearchResults/index.js

Lines 510 to 519 in 4bae51b

	if (state.disjunctiveFacetsRefinements[dfacet]) {
	state.disjunctiveFacetsRefinements[dfacet].forEach(function(refinementValue) {
	// add the disjunctive refinements if it is no more retrieved
	if (!self.disjunctiveFacets[position].data[refinementValue] &&
	state.disjunctiveFacetsRefinements[dfacet].indexOf(unescapeFacetValue(refinementValue)) > -1) {
	self.disjunctiveFacets[position].data[refinementValue] = 0;
	}
	});
	}
	}

[dhayab]

Should we update the unescape util in algolia/react-instantsearch#3420 as well, or are the values cast into strings at that time?

[Haroenv]

3420 is about labels, thus not relevant here :)