fix(analytics): fix refund status filter on dashboard

[tsdk02]

Type of Change

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

Description

• Whenever Refund Status filter is applied on the analytics section on dashboard, errors are being generated.
• The wrong RefundStatus enum has been imported for the RefundStatus filter in RefundFilters struct in this PR: feat(analytics): Add Clickhouse based analytics #2988.
• Updated the code to use the correct RefundStatus import.

Additional Changes

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

Motivation and Context

To fix the issue on dashboard whenever refund status filter is applied.

How did you test it?

• Apply the refund status filter on the dashboard

• Hit the curl:

curl --location 'http://localhost:8080/analytics/v1/org/metrics/refunds' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json' \
--header 'Origin: http://localhost:9000' \
--header 'QueryType: SingleStatTimeseries' \
--header 'Referer: http://localhost:9000/' \
--header 'Sec-Fetch-Dest: empty' \
--header 'Sec-Fetch-Mode: cors' \
--header 'Sec-Fetch-Site: same-site' \
--header 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36' \
--header 'api-key: dev_LZcIA7XeMpnK5satp4CDvjcnHCaeKTBcosyuBBJaknZu1odhFo96cwS0nSdfzuJF' \
--header 'authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiNTQ5ZTNkMmItMTY5Yi00NzUzLWJmNTQtZDcxMTM2YjRiN2JkIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzI2MDQ2MzI4Iiwicm9sZV9pZCI6Im9yZ19hZG1pbiIsImV4cCI6MTcyOTkyOTAwOCwib3JnX2lkIjoib3JnX1ZwU0hPanNZZkR2YWJWWUpnQ0FKIiwicHJvZmlsZV9pZCI6InByb192NXNGb0hlODBPZWlVbElvbm9jTSJ9.B7sxut7HMs1C7QDRJWqOhQXHbugw4Ev3w8EAzskmzeo' \
--header 'sec-ch-ua: "Google Chrome";v="129", "Not=A?Brand";v="8", "Chromium";v="129"' \
--header 'sec-ch-ua-mobile: ?0' \
--header 'sec-ch-ua-platform: "macOS"' \
--data '[
    {
        "timeRange": {
            "startTime": "2024-10-16T18:30:00Z",
            "endTime": "2024-10-24T13:17:00Z"
        },
        "timeSeries": {
            "granularity": "G_ONEDAY"
        },
        "filters": {
            "refund_status": ["success"]
        },
        "mode": "ORDER",
        "source": "BATCH",
        "metrics": [
            "refund_success_rate",
            "refund_count",
            "refund_success_count",
            "refund_processed_amount"
        ]
    }
]'

Respoonse:

{
    "queryData": [
        {
            "refund_success_rate": 100.0,
            "refund_count": 1,
            "refund_success_count": 1,
            "refund_processed_amount": 600,
            "currency": null,
            "refund_status": null,
            "connector": null,
            "refund_type": null,
            "profile_id": null,
            "time_range": {
                "start_time": "2024-10-24T00:00:00.000Z",
                "end_time": "2024-10-24T23:00:00.000Z"
            },
            "time_bucket": "2024-10-24 00:00:00"
        }
    ],
    "metaData": [
        {
            "current_time_range": {
                "start_time": "2024-10-16T18:30:00.000Z",
                "end_time": "2024-10-24T13:17:00.000Z"
            }
        }
    ]
}

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

[semanticdiff-com]

Review changes with SemanticDiff.

Analyzed 1 of 1 files.

Overall, the semantic diff is 50% smaller than the GitHub diff.

	Filename	Status
✔️	crates/api_models/src/analytics/refunds.rs	49.83% smaller