monitoring: register cost services and expose hourly cost metric

[Tobiloba0]

#Closes #616

Summary

Register cost monitoring services to enable collection, tracking, and exposure of the infra_hourly_cost_usd metric for operational dashboards, monitoring, and alerting workflows.

Changes

• Added CostTrackingService to support infrastructure cost metric tracking.
• Added CostSchedulerService to schedule periodic cost metric collection.
• Added AwsCostCollectorService to provide AWS cost data collection capabilities.
• Registered all cost-related services in monitoring.module.ts providers and exports for application-wide availability.

Files Changed

monitoring.module.ts

Testing

Ran monitoring unit tests:

npm test -- --testPathPattern=monitoring -i

All monitoring-related tests passed successfully.

Notes / Follow-ups

• The scheduler currently records a placeholder hourly cost value (0) until cost data integration is completed.

• Future enhancements include:

  • Implementing POST /metrics/cost for local cost metric ingestion and validation.
  • Implementing GET /monitoring/cost/summary for cost reporting and monitoring.
  • Integrating with AWS Cost Explorer to retrieve real infrastructure cost data (requires AWS SDK configuration and appropriate credentials).

#Closes

[RUKAYAT-CODER]

Kindly resolve conflict and fix workflow.

[Tobiloba0]

Maintainer please approve submitted pr

[RUKAYAT-CODER]

Please the conflict is yet to be resolved.
Always pull from the main before pushing

[RUKAYAT-CODER]

Thank you for contributing to the project.

[Tobiloba0]

Hello @RUKAYAT-CODER, I have successfully rebased the branch onto the latest upstream/main entirely and I have resolved the conflicts in monitoring.module.ts, and squashed the redundant build cache commits. The PR history is now clean, linear, and ready for your review. Thanks!