Replaced few TypeError with ValueError in _elementwise_common

[oleksandr-pavlyk]

Used ValueError instead of TypeError per Python guidelines.

Inappropriate uses were pointed out by @vtavana (Thank you)

• 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]

This change was prompted per discussion in #1490

[github-actions]

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

[vtavana]

Thank you, @oleksandr-pavlyk!

[github-actions]

Array API standard conformance tests for dpctl=0.15.1dev3=py310h15de555_7 ran successfully.
Passed: 892
Failed: 17
Skipped: 86

[github-actions]

Array API standard conformance tests for dpctl=0.15.1dev3=py310h15de555_8 ran successfully.
Passed: 891
Failed: 18
Skipped: 86

[coveralls]

coverage: 90.187%. remained the same
when pulling a2ec2f2 on replace-typeerror-with-valueerror-as-appropriate
into fbe0081 on master.

[github-actions]

Array API standard conformance tests for dpctl=0.15.1dev3=py310h15de555_9 ran successfully.
Passed: 891
Failed: 18
Skipped: 86

[github-actions]

Array API standard conformance tests for dpctl=0.15.1dev3=py310h15de555_9 ran successfully.
Passed: 890
Failed: 19
Skipped: 86

[ndgrigorian]

Tests now pass so LGTM! Thanks for this clean up @oleksandr-pavlyk

Other incorrect TypeErrors seem to exist in the project but those can be addressed in separate PRs.