Description

This PR adds runtime validation for the logger option passed to getLogger. If the logger does not implement the required logging methods, the function now logs a warning and falls back to the noopLogger. It can be changed to throw an error, which might lead to a "Breaking change".

Motivation and Context

• The current implementation of getLogger assumes that if a logger is passed, it always matches the expected Logger interface unless the logger option is undefined or its value is null where the original code return (options.logger as Logger) || noopLogger; returns noopLogger.
• This can lead to subtle bugs or runtime errors if the logger is a number, string, or any other object
  Example:

const logger = getLogger({ logger: 500 });
console.log(logger)     // prints 500

How has this been tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.