Explicit shape comparison for dpnp and numpy outputs

[vtavana]

In the test suite, the result arrays from dpnp and numpy were compared, but their shapes were not explicitly checked for equality. As a result, tests could pass even if the shapes differed, such as one being (1,) and the other ().

This PR adds an explicit check to ensure that the output shapes of numpy and dpnp match. Additionally, tests have been updated accordingly to pass with this new check.

• Have you provided a meaningful PR description?
• Have you added a test, reproducer or referred to 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 filing the PR as a draft?

[github-actions]

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

[github-actions]

Array API standard conformance tests for dpnp=0.18.0dev1=py312he4f9c94_5 ran successfully.
Passed: 1221
Failed: 0
Skipped: 10

[coveralls]

coverage: 72.271%. remained the same
when pulling fd343be on compare-shape
into 4c5970b on master.