Refactor: syft error handling

[tcp]

Description

Improves error handling in PySyft by implementing our own result and custom exception.

Proposed changelist for this PR:

• Our own result implementation
• Our own custom error type (SyftException)
• Exception filtering
• Delete PySyftException
  refactor(syft_exc): replace PySyftException with SyftException #8919
• Client and server side handling of service results
  feat(syft_exc): change client and server side response handling #9012
• Update BaseStash and BaseUIDStoreStash
  feat(syft_exc): add implementation of BaseStash and BaseUIDStoreStash using the new types #9013
• Refactor services and stashes
  Refactor/syft error handling services #9018
• Fully integrate with SyftResponseMessage
  • SyftSuccess
  • SyftError
  • Remove SyftException in service/response.py
  • Other SyftResponseMessage subclasses
• Tests are green
• Notebooks are green
• Integration tests are green

Related PRs

• refactor(syft_exc): replace PySyftException with SyftException #8919
• feat(syft_exc): change client and server side response handling #9012
• feat(syft_exc): add implementation of BaseStash and BaseUIDStoreStash using the new types #9013
• Refactor/syft error handling services #9018

Notable changes (TODO)

• {client,server}-side handling of service results
• error handling of client-side methods

How has this been tested?

• Added new tests for Result
• Added new tests for SyftException
• Added tests for ExceptionFilter
• Updated tests
• Current tests are green

Checklist

• I have followed the Contribution Guidelines and Code of Conduct
• I have commented my code following the OpenMined Styleguide
• I have labeled this PR with the relevant Type labels
• My changes are covered by tests

[madhavajay]

How do we send this between worker and backend or other nodes?
Should we consider having a single message exception and then keeping the public / private as kind of twin somewhere?