Refactor Parser Error Handling

[azaleacolburn]

Description

The synthesis parser in the exporter now properly handles the errors it was catching, instead of always printing the stacktrace to the user, it now displays clean errors in most cases. This PR also removes the logging wrapper that was previously being used essentially to wrap everything in a try-catch. Errors now propagate through the parser as values with a new Result class which is inspired by the Rust enum of the same name. Each error contains a message and a severity (Fatal or Warning), the latter refers to the severity on the entire parsing process, so an error might cause a function to completely fail, but the error can be recovered by a parent function. On instantiation, each Err automatically logs itself based on it's severity. For errors that are not even fatal for the originating function, an Err should be instantiated but not returned, as to not break control flow.

Objectives

• Result implementation
• Document Result, Err, and Ok classes
• Replace old error handling with nicer alternative (both for the user and developer)
  • Components.py
  • Materials.py
  • JointHierarchy.py
  • Joints.py
  • PDMessage.py
  • PhysicalProperties.py
  • RigidGroup.py
  • Utilities.py
• Put checks after every opaque fusion function. This should probably be it's own PR.

Testing Done

• Successfully exported Dozer

JIRA Issue