fixed timestamps not respecting overlap when using different audio speed

[Josef-Haupt]

No description provided.

[Copilot]

Pull Request Overview

This PR fixes issues with timestamp calculations when different audio speeds and overlaps are used in the analysis. Key changes include updating tests to verify error conditions for invalid audio speeds and overlaps, modifying the timestamp calculations in the analysis utils, and adding parameter validation for overlap and audio speed in the core parameters setter.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
tests/analyze/test_analyze.py	Updated and added tests to verify error handling for invalid audio_speed and overlap values, and refined expected timestamp calculations.
pyproject.toml	Added pytest-timeout dependency and set a timeout for tests.
birdnet_analyzer/analyze/utils.py	Adjusted timestamp calculations to incorporate audio speed adjustments.
birdnet_analyzer/analyze/core.py	Added parameter validation for overlap and audio_speed.

[Copilot]

[nitpick] Consider adding inline comments to clarify the logic behind calculating step_size and how audio_speed and overlap interact to produce the expected timestamp intervals.

Suggested change

	file_length = 120
	file_length = 120
	# Calculate the step size for timestamp intervals:
	# - 3 * audio_speed: Duration of a segment after speeding up the audio.
	# - overlap * audio_speed: Duration of the overlapping portion between consecutive segments.
	# The step size is the effective interval between the start of consecutive segments.

[Copilot]

Ensure that applying the audio speed multiplier here consistently adjusts the timestamp calculations; adding an inline comment to explain this rationale would improve clarity for future maintainers.