Convert .pxi include files to .pxd/.pyx in dpnp/tensor

[vlad-perevezentsev]

This PR proposes to replace Cython textual includes with proper module imports in dpnp/tensor
.pxi files are converted into corresponding .pxd and .pyx modules for _slicing.pxi, _stride_utils.pxi and _types.pxi`

This change replaces the include .pxi pattern with standard Cython cimport statements and improving modularity

• 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?
• Have you added documentation for your changes, if necessary?
• Have you added your changes to the changelog?

[coveralls]

coverage: 78.38% (-0.06%) from 78.444% — update_tensor_cython_pxi into master

[github-actions]

Array API standard conformance tests for dpnp=0.21.0dev0=py313h509198e_21 ran successfully.
Passed: 1355
Failed: 5
Skipped: 16

[github-actions]

View rendered docs @ https://intelpython.github.io/dpnp/pull/2913/index.html

[antonwolfy]

Is it a good practice to use star cimport?

[antonwolfy]

Does not that produce a circular dependency? (_usmarray ↔ _slicing)

[antonwolfy]

Is there a way to avoid redefinition? To keep the constant defined in single place, the same is applicable to UAR_* constants.

[ndgrigorian]

when these files were in dpctl, my thought was to move these constants into another, separate .pxd which could just be included by both

[vlad-perevezentsev]

@ndgrigorian could you clarify what you mean by a separate .pxd file?
Previously these constants were defined in .pxi files that were included directly into _usmarray.pyx which provided local storage for cdef public api
cimport from another .pxd does not work that (header is generated but constants are zero at runtime)