Fix vectors data on GPU

[svlandeg]

Description

vectors.data can be of type numpy.ndarray or cupy.ndarray, but recent GPU testing highlighted some trouble when using cupy. This PR makes the code more general by relying on current ops, and also avoids using the implicit conversion to scalar by numpy (which cupy doesn't do).

Tested locally, this seemed to fix the trouble from PR #7293 🤞

Types of change

bug fix

Checklist

• I have submitted the spaCy Contributor Agreement.
• I ran the tests, and all new and existing tests passed.
• My changes don't require a change to the documentation, or if they do, I've added all required information.

[adrianeboyd]

I can't seem to add this as a suggestion because it's too far from the existing edits, but after running the GPU tests with all the suggested changes I still run into problems with Vectors.add, I think this PR also needs something like this:

         if vector is not None:
+            xp = get_array_module(self.data)
+            vector = xp.asarray(vector)
             self.data[row] = vector

[svlandeg]

Hm, maybe? I tried to ensure that that wouldn't be necessary in the edits, but we can add it for robustness anyway.

[adrianeboyd]

Maybe I did something wrong, but there are a number of tests that add numpy arrays as the new vector row, which leads to ValueError: non-scalar numpy.ndarray cannot be used for fill, like this:

spaCy/spacy/tests/doc/test_doc_api.py

Lines 235 to 240 in 8b3eec6

	def test_doc_api_has_vector():
	vocab = Vocab()
	vocab.reset_vectors(width=2)
	vocab.set_vector("kitten", vector=numpy.asarray([0.0, 2.0], dtype="f"))
	doc = Doc(vocab, words=["kitten"])
	assert doc.has_vector

I don't think we want to require people using Vector.add to have to provide the new vector with the right ops?

[svlandeg]

Oh shoot, I thought I tracked down most of those tests and changed them to use current ops.
Anyway I already made the change you suggested - does that fix it?