feat: add logTimestamps option for ISO timestamp logging in library

[avi-dev-user]

No description provided.

[ShlomoCode]

Thank you for your contribution!
However, I think adding timestamps at the library level isn’t necessary, since standard runtime orchestrator like Kubernetes, Docker, systemd, PM2 already attach precise timestamps to each log line.
Keeping this responsibility outside the library also allows more flexibility in formatting, localization, and integration with different logging systems.

[ShlomoCode]

If you want, you can achieve this by overriding console.log

[avi-dev-user]

Thanks for the quick response!

I made this opt-in (default: false) specifically because I agree orchestrators handle timestamps well in most cases.

However, we observed a real need in our company: when library logs mix with application logs in aggregated systems, having embedded timestamps makes troubleshooting significantly faster. Overriding console.log globally isn't practical for us since it affects the entire process and conflicts with other libraries.

The implementation is minimal and doesn't impact existing users. Happy to rework it as a custom logger hook if you prefer that approach instead.

[ShlomoCode]

I'm wondering whether to add a logger option (that accepts a function), or to add it to the existing events mechanism.