Fix NoneType error when pulling non existent field
If normalizing a jsonstruct a field can be absent
due to a schema change.

- [X] closes #30148
- [X] tests added / passed
- [X] passes `black pandas`
- [X] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [X] whatsnew entry

Can you add test(s)? Typically the first thing we look for in a PR @WillAyd of course. Test has been added. Thanks for the test. I don't really agree with the change though - why wouldn't you want this to raise a `TypeError`? Imagine if I have 3 records:
```
[{'state': 'Florida', 'info': [1, 2,]}]
[{'state': 'Texas', 'info': None}]
[{'state': 'California', 'info': [2,3,]}]
```

I cannot use json_normalize now with `record_path=['info']` as the field for the second record is None. That's perfectly valid for this field, but not acceptable to pandas. Its a real world case btw.

if the key is not there it should raise a `KeyError` not a `TypeError` I think (I can change the test to verify for that). @WillAyd I have changed it to use the fixture, but I'm not entirely happy with it. The fixture sets it to float('NaN') which is different from 'None'. Now I am testing against an iterable and catching a `TypeError` which changes the gist of it.

What do you think? @jreback @WillAyd ready for re-review @jreback ping Ping @jreback  Friendly reminder @jreback can you merge master and will look again @jreback rebased. Or do you truly want me to merge master into my branch? @jreback all green again. thanks @bolkedebruin very nice