functions that only support finite weights now throw errors for non-finites

[aplavin]

AbstractWeights can contain any values, including NaNs – and many StatsBase functions work with them just fine. But not all, for some like sample it doesn't make sense. So, here I make these functions throw an exception instead of returning a potentially incorrect result.

Some docstrings, like the one for quantile, even explicitly say that

An error is raised if w contains any NaN values.

but this wasn't the case without this PR.

Ideally, NaNs should also be supported by concrete weights types included into StatsBase (#904), but this PR is independent of that.

[aplavin]

Nightly test failures unrelated

[aplavin]

bump...
would be nice to turn silently wrong results into errors here

[aplavin]

another bump...

[aplavin]

and another bump...

[aplavin]

yet another bump...

[aplavin]

yet yet another bump...

[aplavin]

yet yet yet another bump...

[devmotion]

The PR can't be merged? "This branch has conflicts that must be resolved" and tests are failing.

[aplavin]

The PR can't be merged?

Idk the policy here, but saw that you approved these changes 1.5 months ago.

"This branch has conflicts that must be resolved"

I think these conflicts are due to code changes after this PR was created/approved. This is impossible to avoid in advance, of course the longer the PR stays unmerged the more conflicts will appear.
Happy to update & resolve conflicts if you confirm that this PR will be merged after that.

tests are failing

Failures unrelated to changes in this PR:

Error During Test at /home/runner/work/StatsBase.jl/StatsBase.jl/test/scalarstats.jl:227
 Unexpected Pass
 Expression: (#= /home/runner/work/StatsBase.jl/StatsBase.jl/test/scalarstats.jl:227 =# @benchmark(mad($itr))).allocs < 200
 Got correct result, please change to @test if no longer broken.

[aplavin]

yet yet yet yet another bump...

[aplavin]

yet yet yet yet yet another bump...

[aplavin]

yet yet yet yet yet yet another bump...