[Woo POS] Implement message views for location permission

[staskus]

Descriptions

Improvements for IPP flow integrated location permission requests within the TTP and Card Reader process.

Implement message views for POS.

Check PointOfSaleCardPresentPaymentEventPresentationStyle and .locationRequestPreAlert and .locationRequired cases.

• .locationRequestPreAlert is triggered for .nonDetermined location permision state and explains why location is necessary. According to Apple pre-alert guidelines only has a single "Continue" button that requests the location.
• .locationRequired is triggered for .denied location permission state. Display similar or the same information explaining why location is necessary to proceed. IPP also shows Open Settings button for convenience. Consider during the same for POS. Calling dismiss() action cancels the payment flow.

IPP Screenshots

.locationRequestPreAlert	.locationRequired

[dangermattic]

🚫 Please add a type label (e.g. type: enhancement) and a feature label (e.g. feature: stats) to this issue.

[malinajirka]

@staskus I'm not sure I understand what this task is about. What is the impact of not implementing it (aka what is the current behavior in the POS)?

[staskus]

@malinajirka card transactions require location permission for security reasons.

Stripe SDK asks for location permission with a native iOS alert in the middle of the payment process. If merchants deny the permission, real-life payments will fail with an error. Users will have to manually go to settings and enable the permissions.

On IPP, I implemented the functionality where the Woo app takes control of the location-permission process. We ask for the location ourselves and if it's denied we provide a button to open settings directly. This is what Apple had in their TTP requirements.

For POS, it continues to work as before - only the native iOS location alert is shown and the payments could fail with a location permission error. The only complaints I heard about this (for IPP and POS) were from internal testers so far, so I think the impact is low.

Implementation on POS should be easy since we only need to make UI but can reuse all the business logic.