fix: address validation error behavior

[maxwellmattryan]

Summary

Please summarize your changes, describing what they are and why they were made.

Currently validateBech32Address and validateEthereumAddress are returning error strings instead of throwing actual errors.

Changelog

- Change address validation functions to return true if valid or throw error if invalid
- Change logic using address validation functions
- Re-organize crypto util module

Relevant Issues

Please list any related issues using development keywords.

Closes #5240

Testing

Platforms

Please select any platforms where your changes have been tested.

• Desktop
  • MacOS
  • Linux
  • Windows
• Mobile
  • iOS
  • Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

Test recipient address inputs with valid and invalid addresses / strings.

Checklist

Please tick all of the following boxes that are relevant to your changes.

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or modified tests that prove my changes work as intended
• I have verified that new and existing unit tests pass locally with my changes
• I have verified that my latest changes pass CI workflows for testing and linting
• I have made corresponding changes to the documentation

[Tuditi]

Looks good!

[MarkNerdi996]

any reasons for the empty lines?

[Tuditi]

I think Matt added this, since the import comes from another module

[MarkNerdi996]

LGTM