Memory Leak caused by unique Winston categories

When calling winston.loggers.get("category1"), if a logger with the category of "category1" is not found, it will automatically be created.

This means if we run the following code we will create 1000 separate Winston loggers.

for (let i = 0; i < 1000; i++) {
  winston.loggers.get("category" + i);
}

Similarly, when any endpoint is called, the following code is run, resulting in a new Winston logger being created. https://github.com/CyberSource/cybersource-rest-client-node/blob/31baaba047b3efe62e418bd11680599a138644da/src/authentication/logging/Logger.js#L26

To my knowledge, this logger is never closed, and so new Winston loggers pile up on the heap.

Start with src/authentication/logging/Logger.js at line 26 and reproduce the category loop or repeated endpoint calls described in the issue. Trace how Winston loggers are created and retained, then verify that repeated calls no longer cause unbounded logger accumulation.