Fix diagonal() strides calculation for empty results

[antonwolfy]

Previously dpnp.diagonal() returned incorrect strides when the diagonal was empty (e.g., when offset >= array width). The stride was set to itemsize instead of the correct st_n + st_m.

This PR:

• fixes stride calculation to consistently use (st_n + st_m)
• simplifies implementation using unified formula to calculate resulting shape, strides, and offset
• extends tests coverage including scenarios with empty diagonals, views, and non-contiguous arrays

The PR closes #2761.

• 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/index.html

[github-actions]

Array API standard conformance tests for dpnp=0.20.0dev4=py313h509198e_16 ran successfully.
Passed: 1354
Failed: 3
Skipped: 16

[coveralls]

coverage: 81.379% (-0.005%) from 81.384%
when pulling 471bbf8 on resolve-gh-2761
into 54d2109 on master.

[vlad-perevezentsev]

LGTM
Thank you @antonwolfy !