prevent ambiguity when calling take with a Take!R

If Take!R satisfied ```isInputRange!(Unqual!R) && !isInfinite!(Unqual!R) && hasSlicing!(Unqual!R)``` then you would get an ambiguity error calling take!(Take!R)
fix unittest
actually fix the unittest...
Merge pull request #2340 from John-Colvin/patch-9

prevent ambiguity when calling take with a Take!R