fix(connector): [Cryptopay]Remove default case handling for Cryptopay

[prasunna09]

Type of Change

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

Description

Remove default case handling for Cryptopay - Payment Status

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?

Test cases - Make a test payment and test webhooks.
Make an overpaid payment - after redirecting, give more amount, then payment is considered as Overpaid, and then from dashboard, refund it.
Expected behavior - Should get a Unresolved Webhook and then Completed Webhook, and then payment should be succeeded.

Make an Underpaid payment - after redirecting, give less amount, then payment is considered as Underpaid, and then from dashboard, refund it.
Expected behavior - Should get a Unresolved Webhook and then Refunded Webhook, and then payment should be in unresolved.

Make an PaidLate payment - Collect all the transaction details and pay late i.e. after the timer ended, then payment is considered as Paidlate, and then from dashboard, refund it.
Expected behavior - Should get a Unresolved Webhook and then Refunded Webhook, and then payment should be in unresolved.

Checklist

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

[ArjunKarthik]

@prasunna09 Please get clarity on when we can get refunded status from the connector and do the mapping accordingly