MAINT: changes to test_log.py to avoid RuntimeErrors

[oleksandr-pavlyk]

Changed tests to avoid RuntimeErrors issued by NumPy for numerical exceptions

Replaced feeding zeros into dpt.log where it is not essentially for the property tested.

When testing special values, hard code expected results, rather than recompute them with np.log.

• 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?
• If this PR is a work in progress, are you opening the PR as a draft?

[oleksandr-pavlyk]

@antonwolfy For some reason using fixture suppress_invalid_numpy_warnings did not work like it does in "test_sqrt.py".

Perhaps "test_sqrt.py" could use similar type of changes.

[coveralls]

coverage: 83.265%. remained the same when pulling f0d1ec9 on suppress-numpy-warnings-in-test-log into 47f4bc9 on master.

[github-actions]

View rendered docs @ https://intelpython.github.io/dpctl/pulls/1311/index.html

[ndgrigorian]

This is a good change.

Similar changes should be propagated to other tests with warnings.

[github-actions]

Array API standard conformance tests for dpctl=0.14.6dev0=py310h7bf5fec_51 ran successfully.
Passed: 566
Failed: 434
Skipped: 119

[github-actions]

Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞

[github-actions]

Array API standard conformance tests for dpctl=0.14.6dev0=py310h7bf5fec_54 ran successfully.
Passed: 595
Failed: 405
Skipped: 119