"correlation-id" header that is logged should be customizable

💡 Feature request

Is your feature request related to a problem? Please describe

For server-side network calls, there is logging for a header called "correlation-id". This is a useful for tracing, but we do not always have control over the name of headers being used for network calls.

This is the code in question:

one-app/src/server/utils/logging/setup.js

Lines 45 to 49 in 3965956

    
           metaData: { 
        
             method: externalRequest.method, 
        
             // null to explicitly signal no value, undefined if not expected for every request 
        
             correlationId: externalRequest.getHeader('correlation-id') || undefined, 
        
           },

Describe the solution you'd like

An environmental variable to specify the name of the correlation ID header.

Describe alternatives you've considered

Passing a header named "correlation-id" just for logging, assuming it will be ignored by the API we are calling.

Hey @smackfu! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, you can ask in our GitHub Discussions."

Already is 😄
https://github.com/americanexpress/one-app/blob/main/docs/api/modules/App-Configuration.md#configurerequestlog

	metaData: {
	method: externalRequest.method,
	// null to explicitly signal no value, undefined if not expected for every request
	correlationId: externalRequest.getHeader('correlation-id') \|\| undefined,
	},