This checks for potential BLAS issues, which are useful to catch early.

Numpy can now be tested using the standard

    `python -c"import numpy; numpy.test()"`

construct.

The "bench" testing with the old bench files is no longer supported.
These days we use `runtests.py` and `asv`.

The aim here is to separate out the nose dependent files prior to adding
pytest support. This could be done by adding new files to the general
numpy/testing directory, but I felt that it was to have the relevant
files separated out as it makes it easier to completely remove nose
dependencies when needed.

Many places were accessing submodules in numpy/testing directly, and in
some cases incorrectly. That presented a backwards compatibility
problem. The solution adapted here is to have "dummy" files whose
contents will depend on whether of not pytest is active. That way the
module looks the same as before from the outside.

In the case of numpy itself, direct accesses have been fixed. Having
proper `__all__` lists in the submodules helped in that.

The strings in error messages were left untouched

Reloading currently causes problems because global classes defined in
numpy/__init__.py change their identity (a is b) after reload. The
solution taken here is to move those classes to a new non-reloadable
module numpy/_globals and import them into numpy from there.

Classes moved are ModuleDeprecationWarning, VisibleDeprecationWarning,
and _NoValue.

Closes #7844.

There seems to be little use in reloading numpy as any changed modules
that are imported into numpy would need to be reloaded first in order to
see any changes. Furthermore, reloading causes problems as global
classes defined in numpy/__init__.py change their identity. Hence we
raise a RuntimeError when an attempt to reload numpy is made.

Closes #7844.

Give hook to allow platform-specific installs to modify the
initialization of numpy.  Particular use-case is to allow check for SSE2
on Windows when shipping with ATLAS wheel.