chore: Metrics set custom FunctionName cold start dimension

[hjgraca]

Please provide the issue number

Issue number: #784

Summary

Changes

Support setting FunctionName

Decorator

[Metrics(Namespace = "ns", Service = "svc", CaptureColdStart = true, FunctionName= "MyFunctionName")]
 public void HandleWithParamAndLambdaContext(string input, ILambdaContext context)
 {
        
 }

Configure

    Metrics.Configure(options =>
    {
       options.FunctioName = "MyFunctionName";
        options.Namespace = "dotnet-powertools-test";
        options.Service = "testService";
        options.CaptureColdStart = true;
        options.DefaultDimensions = new Dictionary<string, string>
        {
            { "Environment", "Prod" },
            { "Another", "One" }
        };
    });

Builder

_metrics = new MetricsBuilder()
        .WithFunctionName("MyFunctionName")
        .WithCaptureColdStart(true)
        .WithService("testService")
        .WithNamespace("dotnet-powertools-test")
        .WithDefaultDimensions(new Dictionary<string, string>
        {
            { "Environment", "Prod1" },
            { "Another", "One" }
        }).Build();

User experience

Please share what the user experience looks like before and after this change

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 94.44444% with 1 line in your changes missing coverage. Please review.

Project coverage is 74.02%. Comparing base (ce9bf85) to head (75ee06b).
Report is 8 commits behind head on develop.

Files with missing lines	Patch %	Lines
...aries/src/AWS.Lambda.Powertools.Metrics/Metrics.cs	90.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #785      +/-   ##
===========================================
+ Coverage    73.96%   74.02%   +0.05%     
===========================================
  Files          210      210              
  Lines         8381     8396      +15     
  Branches       904      907       +3     
===========================================
+ Hits          6199     6215      +16     
+ Misses        1884     1883       -1     
  Partials       298      298              

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
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