Remove python warnings

[LukasNickel]

• Use logging of the component
• No R1 is expected, so its just debug level
• No DL0 is not expected, so keep it as warning
• Fixes CameraCalibrator warns in case no R1 data is present #2407

[LukasNickel]

Ah sorry, apparently I did not have my pre-commit set up

[morcuended]

thanks @LukasNickel, just a typo in the changelog

[kosack]

Maybe it's not for this PR, but the overall behavior here should be updated to be more in line with how we do the DL1 and DL2 steps. In ctapipe-process, we have methods like should_compute_dl1() that determine if the DL0→DL1 transition should happen or not depending on the existence of pre-existing DL1 or the user specifying it to be recomputed, and same with should_compute_dl2(). It would make more sense to have the same thing for DL0: if DL0 already exists, there should be no need for a warning, but the user should have the option to force re-computing it if and only if R1 also exists.

That way all transitions are handled in the same way, and you only need to deal with the case if the user asks explicitly for a transformation to be re-computed, but the previous data level doesn't exist in the input. And in that case it's not even a warning, but an error that should stop processing.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a2b6072) 92.48% compared to head (de7cb58) 92.47%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2421      +/-   ##
==========================================
- Coverage   92.48%   92.47%   -0.01%     
==========================================
  Files         234      234              
  Lines       19831    19819      -12     
==========================================
- Hits        18340    18328      -12     
  Misses       1491     1491              

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