Adding generated correlation id to response

[Maximys]

Current PR implements issue #61.
Please note that I removed one copy-pasted test that existed before in commit 0f7948d0d65702009e7a85c7228e7cc43af8dc02.

[Copilot]

Pull Request Overview

This PR implements functionality to add a generated correlation ID to the HTTP response headers, addressing issue #61. The change introduces a new addCorrelationIdToResponse parameter that controls whether the correlation ID should be written back to the response.

Key Changes:

• Added a new boolean parameter addCorrelationIdToResponse to control response header population
• Refactored correlation ID resolution logic into separate methods for better maintainability
• Updated all test cases to reflect the new parameter and verify response header behavior

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
CorrelationIdEnricher.cs	Added response header writing capability and refactored correlation ID preparation into dedicated methods
ClientInfoLoggerConfigurationExtensions.cs	Extended API with new addCorrelationIdToResponse parameter
CorrelationIdEnricherTests.cs	Updated all test constructors to use new parameter signature and added assertions for response header verification
appsettings.json	Enabled the new feature in sample application configuration
SampleWebApp.csproj	Changed from package reference to project reference for testing local changes

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The in modifier on the correlationId parameter is unnecessary and provides no benefit for string types. Since strings are immutable reference types, using in doesn't prevent copying or improve performance. Remove the in modifier.

Suggested change

	private void AddCorrelationIdToResponse(HttpContext httpContext, in string correlationId)
	private void AddCorrelationIdToResponse(HttpContext httpContext, string correlationId)

[Copilot]

The nested if-else statements create unnecessary complexity. The inner else block (lines 114-123) can be flattened by combining the conditions or using early returns in the method to improve readability.

Suggested change

	string returnValue;
	if (!string.IsNullOrWhiteSpace(requestHeader))
	{
	returnValue = requestHeader;
	}
	else
	{
	StringValues responseHeader = httpContext.Response.Headers[_headerKey];
	if (!string.IsNullOrWhiteSpace(responseHeader))
	{
	returnValue = responseHeader;
	}
	else
	{
	if (_addValueIfHeaderAbsence)
	{
	returnValue = Guid.NewGuid().ToString();
	}
	else
	{
	returnValue = null;
	}
	}
	}
	return returnValue;
	if (!string.IsNullOrWhiteSpace(requestHeader))
	{
	return requestHeader;
	}
	StringValues responseHeader = httpContext.Response.Headers[_headerKey];
	if (!string.IsNullOrWhiteSpace(responseHeader))
	{
	return responseHeader;
	}
	if (_addValueIfHeaderAbsence)
	{
	return Guid.NewGuid().ToString();
	}
	return null;