BLD/TST: fix bool block failures when strings are passed to replace list
closes #6353

Oh darn this will not pass. This allows different size lists thru
 gotta run will get to this tonight after work
 @jreback This line (from `TestSeries.test_replace`) is masking the same failure, which is a `TypeError` and it in fact should be a `TypeError`, but not because it's trying to index a `bool` object.

``` python
ser = Series(tm.makeTimeSeries().index)
self.assertRaises(TypeError, ser.replace, range(1, 3), [np.nan, 0])
```
 I think we should raise a `TypeError` on these kinds of replacements. It makes no sense to do something like

``` python
s.replace({'asdf': 'fda'})
```

on a `bool` `Series`. I would argue that even something like

``` python
s = Series([True, False])
s.replace({'asdf': 'fda', True: 'abc'})
```

should raise as well, because only part of the replacement is valid. @jreback What do you think?
 Darn, that's not really symmetric with other types though.
 Problem is that the time series behavior is throwing typeerrors for the wrong reasons, but i don't see a general purpose way to fix both this issue and that one without special case one of them
 But since we have to maintain the time series behavior for back compat and the bool behavior is now being defined, i think we should raise a typeerror on any of these kinds of conversions...doing that doesn't break any existing code, but makes it a bit more confusing for users to figure out what works .... e.g.,

``` python
s = Series([True, False])
s.replace({'a': 'b'})
```

will raise, but 

``` python
s.replace('a', 'b')
```

will not
 can you make an entire pass thru on boolean? I think it should just return directly (and if they actually try something like:

```
Series([True,False]).replace(True : 'b')
```

maybe just raise

but all other's will simply pass thru...
?
 should the possibly compare stuff (and raising) just be in mask_missing?
 Tried that already, it breaks things
 ok then

merge when ready
 I'm going to write a bit of docs and release notes first ... just to clarify these somewhat dark corners of the replace API
 github looks back to form now......pls merge when you can....(of course docs good too!)
 looks cool...thanks!
 got that other replace fix coming soon to a pandas repo near you
