Allow to configure log scope key

[laurynasr]

Allow to configure the log scope key for correlation ID property. This allows using a different key, such as ActivityId instead of hardcoded CorrelationId.

The default is CorrelationId as previously; custom key can be set when composing the application with AddCorrelate:

services.AddCorrelate(o => o.LoggingScopeKey = "ActivityId");

[codecov]

Codecov Report

Merging #68 (2f57541) into main (b6b79d5) will increase coverage by 0.21%.
The diff coverage is 96.42%.

Additional details and impacted files

Files	Coverage Δ
...orrelate.AspNetCore/AspNetCore/CorrelateOptions.cs	100.00% <ø> (ø)
...DependencyInjection/ServiceCollectionExtensions.cs	100.00% <100.00%> (ø)
src/Correlate.Core/CorrelationManagerOptions.cs	100.00% <100.00%> (ø)
src/Correlate.Core/Extensions/LoggerExtensions.cs	60.00% <100.00%> (+4.44%)	⬆️
src/Correlate.Core/RootActivity.cs	83.33% <100.00%> (+1.51%)	⬆️
...ependencyInjection/IServiceCollectionExtensions.cs	100.00% <100.00%> (ø)
src/Correlate.Core/CorrelationManager.cs	91.46% <80.00%> (-0.85%)	⬇️

[laurynasr]

@skwasjer is there something else I need to do to get this merged? I see that the automated workflows are waiting for something but I don't know if I should do anything about that

[skwasjer]

@laurynasr no, I just have not had time to look at your proposal yet, will probably do over the weekend. Thanks for the submission.

[skwasjer]

lgtm. The only thing stopping the merge is some missing coverage on the new AddCorrelate() registration extension.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

93.8% Coverage
0.0% Duplication

[skwasjer]

Thanks!