Move logging.basicConfig() out of the library into the CLI entry points

[abeeranajam31]

Closes #259.

Root cause

comet/__init__.py calls logging.basicConfig(level=logging.INFO, format="%(message)s") at import time. basicConfig() configures the root logger for the whole Python process the instant comet (or anything that imports it, like evaluate.load("comet")) is imported — this is the exact anti-pattern Python's own logging docs warn against for libraries.

It's also the concrete reason the workarounds in #259 don't fully work: PyTorch Lightning's various loggers (pytorch_lightning.* / lightning.pytorch.*, the exact names vary by PL version) mostly have no explicit level of their own, so they inherit whatever level the root logger ends up at. comet's import-time basicConfig(INFO) locks that in immediately, so unless a user's code happens to setLevel(ERROR) on the exact right logger name for their installed PL version, some messages leak through — which is exactly what both commenters on #259 ran into (each found a slightly different, incomplete set of logger names to silence).

Verification

This is plain stdlib logging behavior, so it doesn't need a comet install to check:

# current comet behavior: basicConfig(INFO) at import time
>>> logging.basicConfig(level=logging.INFO, format='%(message)s')
>>> logging.getLogger('pytorch_lightning.accelerators.cuda').setLevel(logging.ERROR)  # user silences the logger they know about
>>> logging.getLogger('pytorch_lightning.utilities.rank_zero').info('GPU available: True (cuda), used: True')  # a different PL logger they didn't
GPU available: True (cuda), used: True          # <- still leaks

# fixed: no basicConfig call anywhere
>>> logging.getLogger('pytorch_lightning.utilities.rank_zero').info('GPU available: True (cuda), used: True')
                                                  # <- nothing printed, suppressed by Python's default WARNING+ threshold

The fix

comet/cli/score.py already has a --quiet flag that loops over every registered logger and force-sets it to ERROR — i.e. "verbose INFO logging by default" is already treated as the CLI's choice, not something the importable library should impose on every caller.

So rather than deleting the call outright (which would silently change comet-score's default output), I moved logging.basicConfig(level=logging.INFO, format="%(message)s") into each of the four CLI entry points (score_command, train_command, compare_command, mbr_command). The CLIs keep their exact current default behavior; only library usage changes, letting the calling application configure logging itself, as intended. compare.py and mbr.py didn't import logging at all (they were relying on comet/__init__.py's side effect), so I added it to both.

All 5 changed files pass py_compile.