Fix caplog by enabling log propagation in app logger

[marcgibbons]

Closes #102

The PROJECT_NAME logger had propagate=False and its own console handler to avoid double-logging to the root logger. This also prevented pytest's caplog fixture from capturing app logs, since caplog works by intercepting records at the root logger level.

Fix: remove the redundant console handler from the app logger and set propagate=True. Log records now flow up to the root logger (which owns the console handler), so they reach it exactly once and caplog can capture them as expected.

The PROJECT_NAME logger entry is still needed to set LOG_LEVEL (default INFO) independently from the root logger's WARNING level.

Tests added:

• Root logger: INFO not captured, WARNING captured
• App logger: INFO captured, WARNING captured

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (10f5bcd) to head (43d3911).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #311   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           15        16    +1     
  Lines          324       343   +19     
  Branches         3         3           
=========================================
+ Hits           324       343   +19     

☔ 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.