Issue:#3026 Replaced ValueError and TypeError with InvalidArgumentError

[rounakkraaj-1744]

#3026

Description of changes

• Improvements & Bug fixes
  • Replaced all occurrences of ValueError and TypeError with InvalidArgumentError across the codebase for better error consistency and clarity.

Test plan

• Verified that all test cases pass locally:

  • Run pytest for Python changes.
  • Run yarn test for JavaScript changes.
  • Run cargo test for Rust changes.

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

• Updated docstrings for all affected user-facing APIs to reflect the new InvalidArgumentError usage.
• No changes required in the docs repository.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)