[REFACTOR]: [Airwallex] Remove Default Case Handling

[Sakilmostak]

📝 Feature Description

• We utilize match statements to make pivotal decisions, such as generating requests based on the payment method type and managing responses received from the connector.
• These conditions generally go hand in hand with enum variants.
• Default case is used because a match statement needs to be exhaustive i.e. every variant needs to be covered.
• So, if all the explicit cases are handled then default is used to handle the rest.
• Each connector have these match statements but many of them don’t provide reference to each variant in their default case, rather a _ is put to handle all the other cases.
• This approach carries a risk because developers may inadvertently overlook the need for explicit handling of the new cases.

🔨 Possible Implementation

• Instead of relying on a default match case _, developers should handle each and every variant explicitly.
• By doing so, if there are any changes in the future, they can readily assess the impact of their modifications simply by compiling the code.
• You can check this PR for further reference refactor(connector): [Zen] refactor Zen payment methods not implemented errors #1955

🔖 Note: All the changes needed should be contained within hyperswitch/crates/router/src/connector/

📦 Have you spent some time checking if this feature request has been raised before?

• I checked and didn't find a similar issue

📦 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

✨ Are you willing to submit a PR?

[Vishalk91-4]

@VedantKhairnar, could you please assign this issue to me

[Sakilmostak]

Hello @Vishalk91-4 , I have assigned this issue to you👍

[Sakilmostak]

Hey @Vishalk91-4 it seems like you already have a PR in review which you have not addressed (CI checks not passed). I would suggest to be atleast done with the reviewing of the PR to move on to next

[swangi-kumari]

Hello @Vishalk91-4 ,
Are you still working on this issue?
Please let us know if you need any help:)

[Vishalk91-4]

@swangi-kumari, yes I'm working on it, I'll submit a PR also, a draft PR if you want can be submitted too, actually I was resolving the issue of my PR in hyperswitch in other PR also

[deepanshu-iiitu]

Hey @Vishalk91-4
Just checking in - are you working on it? Do you need help from our side?

[deepanshu-iiitu]

Hello @Vishalk91-4 , we didn't hear back from you, so we are unassigning you from this issue. If you are interested, we will assign you with other issues, if the current one is taken.

[Hangsaai]

Hey @deepanshu-iiitu ,
"Could you please assign this issue to me? My previous PR has been merged, and I want to work on it now."

[Vishalk91-4]

Hello @Vishalk91-4 , we didn't hear back from you, so we are unassigning you from this issue. If you are interested, we will assign you with other issues, if the current one is taken.

Sorry, I'm resolving errors in the other issue in Hyperswitch
#2226

[deepanshu-iiitu]

Hey @Hangsaai , sure! I've assigned this to you.

In case you have any queries, you can ask them on this issue thread, or on our discord server, or on slack whichever you are comfortable with

[swangi-kumari]

Completed in this PR