[DTPP-142] PayPalWebPayments show stages of order

[GMALKHA]

Reason for changes

Summary of changes

Refactored PaypalWebViewModel for better state tracking, updated PayPalButtonsView for progress handling, and fixed successView display issue.

Checklist

• Replaced centralized state management (updateState) with PayPalPaymentState.
• Added individual LoadingState properties for createOrderResponse and approveResultResponse.
• Updated the UI in PayPalButtonsView to check the appropriate LoadingState for progress or error handling.
• Introduced properties like createOrderResponse, approveResultResponse, captureOrderResponse, and authorizedOrderResponse in PaypalPayments for managing states independently.
• Verified that the correct view is displayed after creating an order.

Authors

List GitHub usernames for everyone who contributed to this pull request.

• @GMALKHA

[KunJeongPark]

I think I expected the result of the order creation on the view right below the create order form and above checkout with PayPal.

[KunJeongPark]

Pressing on PayPal checkout button is stuck in loading indicator of Create order button. I'll take a closer look at what's going on.
I think what I expected was separate results view after each state. That was my intention for wanting this, so we can compare results screens of each step.

[KunJeongPark]

Looks good so far, nit picks:

1. this result view could be formatted the same as other views:

2. Loading indicator on the buttons on checkout with PayPal action
3. "Authorize Order" button seems unresponsive - this is because you are acting only on authorized option but observing capture order response on the PayPalWebTransactionView
4. Your viewModel's completeTransaction is only handling authorize option, not capture.

[KunJeongPark]

I'm trying to figure out why your result views for order completion is not appearing while it is working on main.
I see, old updatOrder assigned self.order which assigned OrderID and we are not doing it anymore so completeOrder is not getting called(as it is checking for orderID) We don't need to check for orderID anymore since it is handled in the states.

[GMALKHA]

I'm trying to figure out why your result views for order completion is not appearing while it is working on main. I see, old updatOrder assigned self.order which assigned OrderID and we are not doing it anymore so completeOrder is not getting called(as it is checking for orderID) We don't need to check for orderID anymore since it is handled in the states.

Ah, that was actually something I was planning to refactor yesterday. Right, the orderId is no longer used, and we need to remove a check from there.

[GMALKHA]

I'm trying to figure out why your result views for order completion is not appearing while it is working on main. I see, old updatOrder assigned self.order which assigned OrderID and we are not doing it anymore so completeOrder is not getting called(as it is checking for orderID) We don't need to check for orderID anymore since it is handled in the states.

The loading indicator wasn’t showing because it was tracking the orderID computed property, but it wasn’t assigned in the ViewModel and was always nil. I’ll push a commit to set the orderID

The approve result view is not appearing because the state for approveResultResponse always defaults to idle instead of transitioning to loaded. I'm looking into that.

[KunJeongPark]

Hey Georgi, it looks good so far, just doing some testing. Can you order the views in order they appear?
The main container view, and then order of appearance?

[KunJeongPark]

🎉 Great job Georgi!