Improve exception handling in Engine tracking logic

[mysticBliss]

This PR addresses a code health issue in datamov/core/engine/Engine.py where exceptions during the saving of tracking information were logged without a traceback, making debugging difficult.

Changes:

1. Modified datamov/core/engine/Engine.py:

   • Changed logger.error("Failed to save tracking info: {}".format(e)) to logger.error("Failed to save tracking info", exc_info=True). This ensures the full stack trace is logged.
   • Removed df_tracking.select('dm_etl_uuid', 'load_status').show() to clean up stdout from debug prints.
   • Removed unused variable e in the except block.

2. Updated tests/test_engine.py:

   • Added test_tracking_exception_logging to verify that logger.error is called with exc_info=True when an exception occurs during tracking dataframe creation.

Verification:

• Run PYTHONPATH=. pytest tests/test_engine.py - Passed.
• Verified that tests/test_integration.py failures are unrelated to these changes.

---

PR created automatically by Jules for task 5194203951055708408 started by @mysticBliss

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.