fix(payments): add time range in list payment attempts query

[apoorvdixit88]

Type of Change

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

Description

• Add time range to filter total count for payment attempt list.
• Move TimeRange type to common utils so that it can be used in diesel models and across all the other api models

Additional Changes

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

Motivation and Context

Closes #5958

How did you test it?

The expected behaviour is same, the query that is getting printed, is now also considering time range.

SELECT COUNT(*) FROM "payment_attempt" WHERE ((("payment_attempt"."merchant_id" = $1) 
AND ("payment_attempt"."attempt_id" = ANY($2))) AND ("payment_attempt"."created_at" >= $3)) 
-- binds: [MerchantId("merchant_1726040792"), [], 2024-08-19 18:30:00.0]

Request

curl --location 'http://localhost:8080/payments/list' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer JWT' \
--data '{
    "start_time": "2024-08-19T18:30:00Z"
}'

Response:

{
    "count": 0,
    "total_count": 0,
    "data": []
}

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 40 of 40 files.

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

File Information

	Filename	Status
✔️	crates/storage_impl/src/payouts/payouts.rs	Analyzed
✔️	crates/storage_impl/src/payments/payment_attempt.rs	Analyzed
✔️	crates/storage_impl/src/payments/payment_intent.rs	Analyzed
✔️	crates/storage_impl/src/mock_db/payment_attempt.rs	Analyzed
✔️	crates/storage_impl/src/mock_db/payment_intent.rs	Analyzed
✔️	crates/storage_impl/src/mock_db/payouts.rs	Analyzed
✔️	crates/router/src/types/storage/dispute.rs	Analyzed
✔️	crates/router/src/types/storage/refund.rs	Analyzed
✔️	crates/router/src/types/api/payments.rs	9.09% smaller
✔️	crates/router/src/routes/disputes.rs	Analyzed
✔️	crates/router/src/routes/payments.rs	Analyzed
✔️	crates/router/src/routes/payouts.rs	Analyzed
✔️	crates/router/src/routes/refunds.rs	Analyzed
✔️	crates/router/src/db/dispute.rs	Analyzed
✔️	crates/router/src/db/kafka_store.rs	Analyzed
✔️	crates/router/src/db/refund.rs	Analyzed
✔️	crates/router/src/core/disputes.rs	Analyzed
✔️	crates/router/src/core/payments.rs	Analyzed
✔️	crates/router/src/core/payouts.rs	Analyzed
✔️	crates/router/src/core/refunds.rs	Analyzed
✔️	crates/openapi/src/openapi.rs	25.55% smaller
✔️	crates/openapi/src/openapi_v2.rs	25.55% smaller
✔️	crates/hyperswitch_domain_models/src/payouts.rs	Analyzed
✔️	crates/hyperswitch_domain_models/src/refunds.rs	Analyzed
✔️	crates/hyperswitch_domain_models/src/payouts/payouts.rs	Analyzed
✔️	crates/hyperswitch_domain_models/src/payments/payment_attempt.rs	Analyzed
✔️	crates/hyperswitch_domain_models/src/payments/payment_intent.rs	Analyzed
✔️	crates/diesel_models/src/query/payment_attempt.rs	Analyzed
✔️	crates/common_utils/src/events.rs	Analyzed
✔️	crates/common_utils/src/types.rs	Analyzed
✔️	crates/api_models/src/analytics.rs	Analyzed
✔️	crates/api_models/src/events.rs	Analyzed
✔️	crates/api_models/src/payments.rs	Analyzed
✔️	crates/api_models/src/payouts.rs	Analyzed
✔️	crates/api_models/src/refunds.rs	Analyzed
✔️	crates/api_models/src/analytics/search.rs	Analyzed
✔️	crates/analytics/src/opensearch.rs	51.24% smaller
✔️	crates/analytics/src/disputes/metrics.rs	76.78% smaller
✔️	api-reference-v2/openapi_spec.json	Analyzed
✔️	api-reference/openapi_spec.json	Analyzed