API: consistently raise TypeError for invalid-typed fill_value
- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] passes `black pandas`
- [ ] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] whatsnew entry

This makes us consistent about raising TypeError when passing a wrong-typed fill_value to e.g. `take`.  The downside is that we changed `Categorical.take` from TypeError to ValueError back in 1.1.0 #33660, so theres a bit of whiplash.

The upside (besides this just being More Correct) is that we will be just about fully sharing setitem-like validator methods.
Yea the back and forth is unfortunate, but I agree this seems more correct. Could use a whatsnew note thanks