Kritik Modi

feat(refunds): refactor refund_create_core function in order to support auto-refunds

2

## Type of Change - [x] New feature ## Description This PR refactors the `refund_create_core` function in order to support auto-refunds. ## Motivation and Context This PR closes https://github.com/juspay/hyperswitch/issues/2061. ##...

### Feature Description We cannot use the `refund_create_core` function for issuing an auto-refund since it uses the latest payment attempt. Instead, we need a separate function for processing auto-refunds. ###...

## Type of Change - [x] New feature ## Description This PR adds a new process tracker workflow for processing auto-refunds. ## Motivation and Context This PR closes https://github.com/juspay/hyperswitch/issues/2023. ##...

### Feature Description The auto-refund functionality has to go through the scheduler and hence a new workflow is required for the same. ### Possible Implementation A new workflow can be...

## Type of Change - [x] New feature ## Description This PR adds support for auto-refunds. ## Motivation and Context This PR closes https://github.com/juspay/hyperswitch/issues/2017. ## How did you test it?...

### Feature Description There are some cases in which the payment might not succeed initially and the customer drops out. Then the payment may succeed later and the customer is...

### Feature Description Currently the `payment_method_options` field supports only the `Card` payment method. We need to add support for more payment methods among which Wallet is the highest priority. ###...

### Feature Description `Stripe` now supports a new `capture_method` called `automatic_async` as mentioned [here](https://stripe.com/docs/payments/payment-intents/asynchronous-capture-automatic-async). Hyperswitch doesn't have support for it yet, which will bug out while using the Stripe Compatibility...