Add a threshold for the minimum number of installs to the filter component

i like this tagged with core-post-mvp but I am wary that we'll be able to identify the threshold of what the actual number is that makes it valid and worthwhile. I tend to think _sorting_ by popularity (desc) solves the use case better.

sorting just by popularity wouldn't be the same like having such a threshold plus the sorting by popularity ascending. without the threshold you might have a long, a very long, tail of modules with 1 or 15 installs for some searches. and a user might consider a small number of installs not trustworthy enough. with sorted by popularity in descending order you only get the big common ones. by sorting in ascending order you get the long tail but within that long tail there might be some hidden gems. by providing the ability to have a lower threshold of a minimum number of installs the user would be able based on context to individually change that threshold. for one search query the structure of search results it would be reasonable to set that threshold to 50 for another search to 100 or one users says in general all modules i want to considers should have at least the number of x installs.

I will try to get some discussion on this in today's meeting. I can see the value, but I also don't want to clutter the UI with a text field (or would we have some sort of dropdown / bracketing: minimum of 10: 100: 1000?). Of course it would go in the advanced filters dropdown, which somewhat mitigates it...

I think this is something we can wait to see if the users clamor for it once it's in core as experimental (or beyond) before dedicated effort to it.