refactor(api_models): follow naming convention for wallets & paylater payment method data enums

[ArjunKarthik]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Payment method data enums should follow naming conventions, like if it is Redirect flow then name should be "{Payment_Method_Name}Redirect"

Updated api contract

AliPay Redirect:
"payment_method_data": { "wallet": { "ali_pay_redirect": {} } }

WechatPay Redirect:
"payment_method_data": { "wallet": { "we_chat_pay_redirect": {} } }

MBWay Redirect:
"payment_method_data": { "wallet": { "mb_way_redirect": { "telephone_number":"+351213822199" } } }

Walley Redirect:
"payment_method_data": { "pay_later": { "walley_redirect": {} } }

PayBright Redirect:
"payment_method_data": { "pay_later": { "pay_bright_redirect": {} } }

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Postman:

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable