[UAT] Allow payment methods

Basic scenarios:

1. Sanity

2. Default status

3. Activate and deactivate payment methods in one restaurant

4. Check the restaurant in Whitelabel

5. Activate and deactivate payment methods in two or more restaurants

6. Check the restaurants in Whitelabel

7. Cash limitation prioritization

Important points:

1. Default status:

   1. When the feature is deployed on the environment and the payment method is added on the Sanity, the payment method is created on DOP with the default status as "Null".

   2. However, even if the status is "Null", if the payment method is Enabled on Launch Darkly, the payment method will continue to be listed on the dropdown. In order to deactivate the payment method, it is necessary to deactivate by DOP and save.

   3. Regarding rolling out this feature, we recommend a bulk update in all restaurants in each market.

   4. For new restaurants, it will be necessary to edit and save.

2. Payment method dropdown caching

   1. There is an existing caching on the payment method dropdown in the user session. So after a payment method is activated or deactivated via DOP, the update will reflect if the user reloads the page or reopens the app. This behavior already happens in other places in the Whitelabel. Still, we are refining a solution to fix this on the dropdown as we also implemented the cash limitation feature.

3. Launch Darkly > Cash limitation > Allow payment methods prioritization

   1. The Launch Darkly always will have priority, if a payment method is disabled there and enabled on DOP, the payment method will not be displayed on the Whitelabel.

4. The modal update confirmation

   1. The modal update confirmation is already implemented on the cash limitation only when the user is updating two or more restaurants. We keep this behavior on the allow payments as well.

5. Translation payment methods on DOP

   1. The payment methods title displayed on the DOP page is getting the translation from Lokalise. Just in case it is necessary to customize it, we will have to implement this.