Support tuple of integers for axis in dpnp.trim_zeros

[antonwolfy]

The PR aligns with NumPy 2.4 change and adds support for tuple of integers passed with axis argument in dpnp.trim_zeros

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

[github-actions]

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

[coveralls]

coverage: 81.103% (-0.001%) from 81.104%
when pulling 1775a82 on support-axis-sequence-in-trim_zeros
into 869ccb8 on master.

[github-actions]

Array API standard conformance tests for dpnp=0.20.0dev2=py313h509198e_15 ran successfully.
Passed: 1227
Failed: 0
Skipped: 9

[vlad-perevezentsev]

Incorrect shape for empty input with Numpy 2.4

a = numpy.empty((0,3))
a_dp = dpnp.empty((0,3))

numpy.trim_zeros(a,axis=None).shape
# (0, 0)

dpnp.trim_zeros(a_dp, axis=None).shape
# (0, 3)

[antonwolfy]

It seems more as a bug in NumPy implementation which existed before 2.4 release as well.
An empty array does not contain any zero elements, so there is nothing to trim. IMHO it is correct to return the input array unchanged then.

[vlad-perevezentsev]

@antonwolfy could you add a test that shows different behavior with NumPy and a comment for it?

[antonwolfy]

I added a test to cover dpnp behavior with 0-sized input array.
I don't see a reason to check the NumPy behavior, if it's faulty.