fix(core): introduce new attempt and intent status to handle multiple partial captures

[hrithikesh026]

Type of Change

• Bugfix

Description

• Add PartiallyCapturedAndCapturable enum type to IntentStatus
• Add PartialChargedAndChargeable enum type to AttemptStatus

(1) Currently, single 'manual' capture results in 'succeeded'(intent) and 'charged'(attempt) statuses during a successful full/partial capture.

(2) 'Multiple manual' capture results in:
(a) 'partially captured'(intent) and 'partially charged'(attempt) when amount_capturable>0
(b) 'succeeded' (intent) and 'charged' (attempt) statuses when amount_capturable=0 after a successful capture
(c) 'succeeded'(intent) and 'voided'(attempt) when a void call is made after at least one successful partial capture
(d) 'cancelled'(attempt) and 'voided'(intent) when a void call is made even before one successful partial capture

In order to address the incongruity in intent vs attempt statuses in (2)(c) case, we would need to introduce another set of non-terminal statuses ['partially captured and capturable' (intent); 'partially captured and capturable'(attempt)] which would be mapped to (2)(a) case above whereas the 'partially captured'(intent) and 'partially charged'(attempt) statuses would be mapped to (2)(c) case.

Even in case of single 'partial' captures, the statuses should be updated to 'partially captured'(intent) and 'partially charged'(attempt).

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?

Manual

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

[pixincreate]

Added what I observed..

[pixincreate]

Kindly check the deployment readiness.

[pixincreate]

@SanchithHegde, can you look into deployment readiness being unresponsive (I believe, it is the same issue that we observed yesterday. Waits for hours.) here in merge queue?