[Issue]: catch to low DummyChapterDuration

[jumoog]

Please describe your bug

For 10.9, DummyChapterDuration was disabled. If you want it to be reanable, it is not clear that you have to enter seconds in the settings. So I set it to 2. This resulted in 100% IO and CPU utilisation. We should catch user errors, e.g. only allow a minimum of 1 minute and describe in the UI that this value is in seconds. I didn't have the commit back then: f77a5d0

Reproduction Steps

Set DummyChapterDuration to 2 and scan a library that has DummyChapterDuration enabled.

Jellyfin Version

10.9.0

if other:

No response

Environment

- Virtualization: Docker

Jellyfin logs

no logs

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[jellyfin-bot]

Hi, it seems like your issue report has the following item(s) that need to be addressed:

• The format of the environment section has been altered from the template.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

[jumoog]

I could not cancel the scan. Only a higher value and a Docker reboot helped.