RPP / Failures / Catch exceptions and generate erroneous states

[RadoslavGeorgiev]

Description

The current payment process throws exceptions upon all sorts of failure, and has a single block to catch all of them.

The new payment process should handle exceptions at a more granular level, and switch to a failure state immediately.

Acceptance criteria

• Generic exceptions (Exception, Order_Not_Found, etc.) are handled within the payment processing service, rather than within a state, entering SystemErrorState.
• Specific exceptions (ex. those around requests) should be handled immediately.
• The error states should contain the needed functionality to log the errors, and mark the order as failed if needed.

Testing instructions

All thrown exceptions should be caught.

Dev notes

For now, we can focus only on the exceptions we are already aware of through Psalm.

Additional context

Epic: #6673
Project: paJDYF-9hL-p2

[RadoslavGeorgiev]

Marking as blocked because of Gamma's shift of current priorities.