Fix bug in basic slicing of empty arrays

[oleksandr-pavlyk]

Reproducer provided by @ndgrigorian:

import dpctl.tensor as dpt
x = dpt.ones((0, 10))
y = dpt.moveaxis(x, 1, 0)
y[1] # raises ValueError

Now this returns empty 1d array like y[0] does.

A test is added for both integral basic indexing,
and for simple slice.

---

• Have you provided a meaningful PR description?
• Have you added a test, reproducer or referred to an issue with a reproducer?
• Have you tested your changes locally for CPU and GPU devices?
• Have you made sure that new changes do not introduce compiler warnings?
• Have you checked performance impact of proposed changes?
• If this PR is a work in progress, are you opening the PR as a draft?

[github-actions]

Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞

[coveralls]

coverage: 87.953% (+0.005%) from 87.948%
when pulling 9fa1aec on fix-basic-slicing-on-empty-arrays
into d840cee on master.

[github-actions]

Array API standard conformance tests for dpctl=0.17.0dev0=py310h15de555_353 ran successfully.
Passed: 889
Failed: 16
Skipped: 91

[github-actions]

Array API standard conformance tests for dpctl=0.17.0dev0=py310h15de555_353 ran successfully.
Passed: 889
Failed: 16
Skipped: 91

[ndgrigorian]

This resolves the array API test failure. I've also tested it out in some edge cases and it seems to work as intended.

In [1]: import dpctl.tensor as dpt, dpctl, numpy as np

In [2]: x = dpt.arange(100, dtype="f4")

In [3]: x1 = dpt.reshape(x[2:], (7, 14))

In [4]: x1[-1:0, :].mT[2]
Out[4]: usm_ndarray([], dtype=float32)

In [5]: _.shape
Out[5]: (0,)

In [6]: test = x1[-1:0, :]

In [7]: test.shape
Out[7]: (0, 14)

In [8]: test.shape = (0, 100)

In [9]: test.mT[2]
Out[9]: usm_ndarray([], dtype=float32)

In [10]: test[:, 2]
Out[10]: usm_ndarray([], dtype=float32)

Windows CI break is unrelated...