BREAKING(log): remove NOTSET LogLevel

[timreichen]

Changes
This PR removes the NOTSET LogLevel.

Reasoning
Instead of NOTSET loggers should be initialized with the default set LogLevel (which is INFO).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.56%. Comparing base (93e0cd6) to head (ab0ddd3).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6078   +/-   ##
=======================================
  Coverage   96.56%   96.56%           
=======================================
  Files         532      532           
  Lines       40819    40818    -1     
  Branches     6111     6111           
=======================================
  Hits        39416    39416           
  Misses       1360     1360           
+ Partials       43       42    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[kt3k]

There seem some dependencies to this symbol. https://github.com/search?q=NOTSET+language%3ATypeScript+std%2Flog&type=code

I don't find much value to this change, while it has some negative effects to the above users.

[timreichen]

The log module is not stable, so breaking changes for v1 should not be a dealbreaker imo.
To me this seems to be a question of principal: Does NOTSET as a loglevel make sense in the ts/js context? I would argue no. WDYT?

[kt3k]

The created logger doesn't have any handler. It means the logger doesn't do anything. I wonder if this change would impact the user in any meaningful way..