feat(router): add v2 endpoint retrieve payment aggregate based on merchant profile

[aniketburman014]

Type of Change

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

Description

Add Aggregate API which enables merchants to retrieve summarized payment data based on a specified date range at profile or merchant level. The API aggregates key payment metrics, such as total transaction count, total processed amount, and status breakdown, helping merchants analyze their payment performance effectively.

Key Changes

pub async fn get_payments_aggregates_profile -> crates/router/src/routes/payments.rs - this implementation extracts the profile ID directly from the authentication data, ensuring profile-based filtering of payment aggregates.

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?

• Curl
  curl --location 'http://localhost:8080/v2/payments/aggregate?start_time=2025-01-05T18%3A30%3A00Z&end_time=2025-02-05T08%3A59%3A00Z' \ --header 'X-Profile-Id: pro_68rBAUSCoq91kQ870GFR' \ --header 'api-key: dev_elV1dBHRfYgbT09Q3R914ZOZzKCsJFjMJRot4TUcByFCYDseSZHTrZbCJuBX6ZHO'

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  

Changed Files

File	Status
crates/router/src/db/kafka_store.rs	79% smaller
crates/router/src/routes/app.rs	14% smaller
crates/hyperswitch_domain_models/src/payments/payment_intent.rs	5% smaller
crates/storage_impl/src/mock_db/payment_intent.rs	5% smaller
crates/storage_impl/src/payments/payment_intent.rs	5% smaller
crates/router/src/core/payments.rs	0% smaller
crates/router/src/routes/payments.rs	0% smaller

[SanchithHegde]

Should this have been ProfilePaymentRead?

[SanchithHegde]

Nit: You can combine with the previous routes being registered.

Suggested change

	);
	route = route.service(
	web::resource("/aggregate").route(web::get().to(payments::get_payments_aggregates)),
	);
	)
	.service(
	web::resource("/aggregate").route(web::get().to(payments::get_payments_aggregates)),
	);

[apoorvdixit88]

In V1 we have two routes for aggregate, one is merchant level other is at profile level, we should have in V2 as well? here