Avoid logging in __del__ functions

[ehsantn]

Changes included in this PR

Fixes an issue I noticed when running examples on an AWS instance.

Exception ignored in: <function LazyArrowExtensionArray.__del__ at 0x7fc6700efb00>
Traceback (most recent call last):
  File "/home/bodo/.conda/envs/Bodo120/lib/python3.12/site-packages/bodo/pandas/arrow/array.py", line 131, in __del__
  File "/home/bodo/.conda/envs/Bodo120/lib/python3.12/site-packages/bodo/submit/utils.py", line 49, in debug_msg
AttributeError: 'NoneType' object has no attribute 'user_logging'

I think it's because logging during atexit is not safe. Adding logs here isn't that critical anyways.

Testing strategy

User facing changes

Checklist

• Pipelines passed before requesting review. To run CI you must include [run CI] in your commit message.
• I am familiar with the Contributing Guide
• I have installed + ran pre-commit hooks.

[IsaacWarren]

Thanks Ehsan

[scott-routledge2]

LGTM! In spawner.reset we also do some logging but it's in a try/except