Resolve compute follows data issue in logspace and geomspace functions

[antonwolfy]

The PR closes #2352 and closes #2353.

This PR improves implementation of dpnp.logspace and dpnp.geomspace functions based on the latest changes added to NumPy.
And it also updates logic of how input array_like arguments handled to follow compute follows data approach.
If no device or sycl_queue keyword passed, then an array creation function should allocate result based on input arguments (like start and stop).
Otherwise all input arrays need to be moved to the specified queue and resulting array must be allocated there.

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

[github-actions]

Array API standard conformance tests for dpnp=0.20.0dev1=py313h509198e_46 ran successfully.
Passed: 1229
Failed: 0
Skipped: 7

[coveralls]

coverage: 81.326% (-0.01%) from 81.336%
when pulling 8f2b44c on resolve-gh-2352-2353
into 290ab65 on master.