Apply w/a for expected result in spacing test only on non-Intel NumPy

[antonwolfy]

The stock NumPy returns incorrect result for numpy.spacing(-0.0), while Intel NumPy returns the expected one (the same as dpnp also).
It might be the case when dpnp test is running with the stock NumPy. Thus the PR add a conditional check to update expected result in TestSpacing::test_zeros in case when non-Intel NumPy is used.

Previously the same logic was based on NumPy version, assuming Intel NumPy has always version < "2.0.0", but it is not the case anymore.

• 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

[coveralls]

coverage: 71.711%. remained the same
when pulling 8b100d9 on resolve-issue-with-spacing-tests
into fdf9ba7 on master.

[github-actions]

Array API standard conformance tests for dpnp=0.18.0dev2=py312he4f9c94_22 ran successfully.
Passed: 1229
Failed: 0
Skipped: 9

[vtavana]

Thank you, @antonwolfy!