chore: Metrics AspNetCore support

[hjgraca]

Please provide the issue number

Issue number: #773

Summary

Changes

This pull request introduces a new library for capturing and publishing custom metrics from AWS Lambda functions using ASP.NET Core. The key changes include adding project references, creating new classes for metrics handling, and updating documentation.

New Library AWS.Lambda.Powertools.Metrics.AspNetCore

New Library Introduction:

• AWS.Lambda.Powertools.Metrics.AspNetCore: Added new project for ASP.NET Core metrics handling.
• AWS.Lambda.Powertools.Metrics.AspNetCore.Tests: Added new project for testing the ASP.NET Core metrics library.

Metrics Handling:

• Http/MetricsEndpointExtensions.cs: Added extension methods for route handlers to include metrics filters.
• Http/MetricsFilter.cs: Created a filter class to capture and record metrics for HTTP endpoints.
• Http/MetricsHelper.cs: Introduced a helper class to capture cold start metrics and record them.
• Http/MetricsMiddlewareExtensions.cs: Added middleware extension methods to capture metrics for HTTP requests.

Documentation:

• README.md: Provided detailed usage instructions and examples for the new ASP.NET Core metrics library.

Solution Configuration:

• AWS.Lambda.Powertools.sln: Updated the solution file to include the new ASP.NET Core metrics projects and their configurations. [1] [2]

User experience

Checklist

Please leave checklist items unchecked if they do not apply to your change.

• Meets tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[codecov]

Codecov Report

Attention: Patch coverage is 86.53846% with 14 lines in your changes missing coverage. Please review.

Project coverage is 73.95%. Comparing base (b0d8807) to head (367d990).
Report is 28 commits behind head on develop.

Files with missing lines	Patch %	Lines
...owertools.Metrics.AspNetCore/Http/MetricsFilter.cs	62.50%	6 Missing ⚠️
...aries/src/AWS.Lambda.Powertools.Metrics/Metrics.cs	86.84%	2 Missing and 3 partials ⚠️
...WS.Lambda.Powertools.Common/Core/ConsoleWrapper.cs	75.00%	1 Missing ⚠️
...rtools.Metrics.AspNetCore/Http/ColdStartTracker.cs	95.83%	0 Missing and 1 partial ⚠️
...ambda.Powertools.Metrics/Internal/MetricsAspect.cs	66.66%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #775      +/-   ##
===========================================
+ Coverage    73.82%   73.95%   +0.13%     
===========================================
  Files          205      210       +5     
  Lines         8324     8378      +54     
  Branches       901      904       +3     
===========================================
+ Hits          6145     6196      +51     
  Misses        1884     1884              
- Partials       295      298       +3     

Flag	Coverage Δ
unittests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[leandrodamascena]

SUPER NICE WORK @hjgraca! I just left some small comments before you merge it!

[leandrodamascena]

APPROVED!!!

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud