feat: Add support for output_frequency to write less output

[b8raoult]

Allow users to write only certain steps. The frequency can be set globally or per output.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.03%. Comparing base (e89974c) to head (39497f3).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #109   +/-   ##
========================================
  Coverage    98.03%   98.03%           
========================================
  Files            3        3           
  Lines           51       51           
========================================
  Hits            50       50           
  Misses           1        1           

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

[dietervdb-meteo]

Suggested change

	"""This method should be be called directly
	"""This method should not be called directly

[dietervdb-meteo]

Should it be enforced/checked that output_frequency is a multiple of the model timestep? In the current implementation one can set up a 24h lead time inference, put output_frequency=4 or output_frequency=5 for a 6h step model and inference will run without problems. In the first case the actual output_frequency will be 12, the lcm, while in the second case no output will be generated since the lcm, 30, is outside of the lead time.