instead of `import numpy.testing as npt`.

- all of NumPy's own tests themselves use the from-import variant
- There's `import numpy.typing as npt` around in some places so
  we should not abbreviate another module import with `npt`.

Optional further enhancement: If this is a convention we also want
users to adopt, this should be mentioned in the module docstring of
`numpy.testing`.

ENH: Use new argument parsing for array creation functions

The array creation functions have the most to gain:

1. np.asarray is 4 times faster and commonly used.
2. Other functions are wrapped using __array_function__ in Python
   making it more difficult

This commit (unfortunatly) has to do a few things:

* Modify __array_function__ C-side dispatching to accomodate
  the fastcall argument convention.
* Move asarray, etc. to C after removing all "fast paths" from
  np.array (simplifying the code)
* Fixup imports, since asarray was imported directly in a few places
* Replace some places where `np.array` was probably used for speed
  instead of np.asarray or similar. (or by accident in 1 or 2 places)

This update a coupe of references (single backticks) that actually are not to
verbatim/code (double backticks); and a couple of verbatim to reference
when they do actually exists and can be resolved in context.

I probably missed other; and stayed simple but spoted a few other
inconsistencies that I did not fix:

  - some ``...`` could actually be :math:`...` but not always clear if
  it would be better.
  - some intervals are [``...``], other are ``[...]``

I guess they could be discussed individually; it was mostly the failing
references that bothered me.