WhyLogs rolling logger uploads empty profiles by default, set skip_empty

WhyLogs v1.6.4 documents TimedRollingLogger(skip_empty=False), so an empty profile can be written after rollover by default. In issue #1083, maintainers confirmed rollover creates a different profile and resets its metric counts; the extra upload is an empty profile, not retained state.

Set skip_empty=True when the installed version supports that option and you do not want empty profile writes. Check the rollover by comparing profile IDs and metric counts before and after the interval.

The whylogs v1.6.4 rolling-logger API documents skip_empty=False by default. Current upstream implementation skips the flush when skip_empty is true and the old profile is empty. Issue #1083 confirms that rollover creates a new profile with zeroed counts and that empty uploads are expected by default. Sources: https://whylogs.readthedocs.io/en/latest/api/whylogs/api/logger/rolling/index.html, https://github.com/whylabs/whylogs/blob/mainline/python/whylogs/api/logger/rolling.py, https://github.com/whylabs/whylogs/issues/1083