DEP: Deprecate NumPy object scalars
DEP: Deprecate NumPy object scalars

NumPy object scalars should not exist, since they should always
just return the actual scalar in the first place. Put a deprecation
warning in place to be rapidly changed into a TypeError.

Once allocating it gives an error, we can make all methods raise
errors (with the exception of `__new__`.

jakirkham/numpy,mhvk/numpy,simongibbons/numpy,grlee77/numpy,rgommers/numpy,numpy/numpy,madphysicist/numpy,charris/numpy,mhvk/numpy,mhvk/numpy,madphysicist/numpy,seberg/numpy,rgommers/numpy,jakirkham/numpy,pbrod/numpy,pbrod/numpy,grlee77/numpy,jakirkham/numpy,anntzer/numpy,mhvk/numpy,grlee77/numpy,anntzer/numpy,pbrod/numpy,pdebuyl/numpy,mattip/numpy,pdebuyl/numpy,anntzer/numpy,numpy/numpy,seberg/numpy,madphysicist/numpy,mattip/numpy,madphysicist/numpy,simongibbons/numpy,endolith/numpy,rgommers/numpy,anntzer/numpy,pdebuyl/numpy,jakirkham/numpy,pbrod/numpy,seberg/numpy,madphysicist/numpy,grlee77/numpy,simongibbons/numpy,seberg/numpy,endolith/numpy,numpy/numpy,mattip/numpy,endolith/numpy,simongibbons/numpy,simongibbons/numpy,charris/numpy,jakirkham/numpy,charris/numpy,grlee77/numpy,rgommers/numpy,mattip/numpy,numpy/numpy,pbrod/numpy,endolith/numpy,charris/numpy,pdebuyl/numpy,mhvk/numpy