Fix implementation of dpctl.tensor.moveaxis()

[vtavana]

closes #1173
Fixes an error related to dpt.moveaxis and adds new tests from numpy

• 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]

Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_115 ran successfully.
Passed: 47
Failed: 787
Skipped: 282

[coveralls]

Coverage: 83.263% (+0.009%) from 83.254% when pulling 15e5e73 on fix_moveaxis_error into b050e8c on master.

[github-actions]

View rendered docs @ https://intelpython.github.io/dpctl/pulls/1174/index.html

[github-actions]

Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_115 ran successfully.
Passed: 47
Failed: 787
Skipped: 282

[github-actions]

Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_115 ran successfully.
Passed: 47
Failed: 787
Skipped: 282

[oleksandr-pavlyk]

Right now the complexity is quadratic in the size of destination tuple, but luckily this size is bounded for meaningful applications.

[github-actions]

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

[github-actions]

Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_115 ran successfully.
Passed: 47
Failed: 787
Skipped: 282