Deprecate the DeviceNDArray class and public APIs that return instances

[brandon-b-miller]

Part of #471

• Adds a DeprecatedNDArrayAPIWarning emitted from all user facing functions for moving data around (cuda.to_device, driver.host_to_device, device_to_host, also as_cuda_array, is_cuda_array, etc
• Separates existing now deprecated APIs into internal non-warning versions and external warning versions
• Adds a deprecation warning to the DeviceNDArray ctor
• Separates DeviceNDArray into a functionally equivalent internal class that doesn't warn and a public wrapper that does warn
• Removes as many usages of the deprecated APIs as possible from the test suite in favor of cupy arrays
• Catches warnings for tests of the currently exposed and now deprecated APIs
• Where absolutely necessary, tests calls internal non-warning versions of the deprecated APIs
• Rework tests to not use these apis as much as possible

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[cpcloud]

cupy arrays are much slower than DeviceNDArray because they require creating an external (i.e., non-numba-cuda-created) stream, so I'm not sure a recommendation for that is what we should do right now.

I was thinking that we can keep the top-level APIs (device_array etc.) and replace their internals with StridedMemoryView or something similar, in an effort to allow folks to as-cheaply-as-possible construct arrays.

[cpcloud]

Here's the current state of the art:

[brandon-b-miller]

I concur that a light weight device array like container should exist, I'm just not sure that numba-cuda should necessarily be the library providing it publicly. I think we should nudge users away from using numba-cuda as such, like for moving data from host to device. That said, I'm open to suggestions on what we should recommend.