Add command to stop time exceeding timesheets

[binsky08]

Description

Currently there's no option to automatically stop timesheets, you forgot to stop manually.
If you have something like a company rule for a maximum work time per timesheets (or you're just forgetful :D), the implemented command helps enforcing that.

---

This pull request adds a command that stops timesheets with a duration longer than the specified amount of hours (as command argument), if they do not yet have an end value set.

---

Example usage would be a cron job that runs the command once a hour like:
bin/console kimai:timesheet:stop-time-exceeding 12 to disallow timesheets longer than 12 hours.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I verified that my code applies to the guidelines (composer code-check)
• I updated the documentation (see here)
• I agree that this code is used in Kimai (see license)

[CLAassistant]

All committers have signed the CLA.

[kevinpapst]

Thanks for taking the time to share your solution 👍

I have several issues with this.
A command can only be used from a cron-jobs, an API method would be better to make it more versatile.

Then there are already both an API method that allows to find active timesheets and one to stop a timesheet.
There is a system configuration for the max allowed duration of a timesheet.

Can you please move the logic to a service method, and use the existing system configuration as default option (instead of a required duration input) we can talk .