[MINOR] Reduce logging in MLContextTests

[Baunsgaard]

There are some PRs that fail on MLContextTests, and i saw they produce over 80k logging.
Therefore, to test my new setup, here is a PR that reduce this.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.39%. Comparing base (3f7b17b) to head (1fa95a1).

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2432      +/-   ##
============================================
- Coverage     71.55%   71.39%   -0.16%     
+ Complexity    47461    47368      -93     
============================================
  Files          1539     1539              
  Lines        182631   182631              
  Branches      35919    35919              
============================================
- Hits         130677   130397     -280     
- Misses        41944    42184     +240     
- Partials      10010    10050      +40     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[e-strauss]

lgtm, now you can read again the logs in the github actions without downloading them :)

[e-strauss]

how would enabling the tracing, would help with code coverage anyways? is there conditional code on log level?

[Baunsgaard]

It is a bit annoying but people do this if we are not carefull.

In essence, many places use :

if(LOG.isDebug()) {
 // some code
}

This means code coverage will be low, unless we explicity enable the logging.

We can circumvent it by having explicit logging tests, instead of just fully enabling logging.