refactor: navigations flow. planning for screens to take the full object instead of selective properties. This is to avoid basic crashes that may happen when one piece of data is missing through the navigation. and some biome formatting.

refactor: navigations flow. planning for screens to take the full object instead of selective properties. This is to avoid basic crashes that may happen when one piece of data is missing through the navigation.

Some files where impacted so changes where applied there too.

using appstate to listen to browser closing. Current implementation is wack tho. waiting for the api to be fixed to handle response properly

decoupled the function; add a checkStatus function that will do the job and return a string if an errror occured

With this update i can persist the switch values for the different operators using the modal and the useTransactionHistory Hook.

should avoid closing the modal here since the whole execution is async. This close would have been executed without waiting

the navigation to the result screen when the orange transaction is a success is handled by the hook itself. this solve the issue with navigation still happening even tho the transaction was in progress or failed

show information modal when payment is still in progress and give the opportunity to the user to retry (opening the browser again).

add mutation for checking transaction status after the browser is dismissed. the check is done 3 times unless success or failed is returned from the response.
Change the flow logic of mutations to make it more predictable.

- export mutation handler for request retrieving payment url