Adds new command to reset stuck invalidations

[sgiehl]

Description:

Adds a new command to allow administrators to reset stuck invalidations that are incorrectly marked as "in progress."

Stuck invalidations can happen if an archiving process was interrupted, such as during a server crash or deployment, leaving invalidations in a stuck state. Resetting them ensures they can be reprocessed in the next archiving run.

Usage examples:

• Reset all stuck invalidations for site ID 1 that were started more than an hour ago:
  ./console core:reset-invalidations --idsite=1 --older-than="1 hour ago"

• Reset invalidations assigned to a specific host:
  ./console core:reset-invalidations --processing-host=archiver1.example.com

• Perform a dry run to check which invalidations would be reset:
  ./console core:reset-invalidations --idsite=1 --older-than="1 hour ago" --dry-run

• Reset invalidations for multiple sites and hosts:
  ./console core:reset-invalidations --idsite=1 --idsite=10 --processing-host=archiver1 --processing-host=archiver2

fixes #22971

Review

• Functional review done
• Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
• Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
• Security review done
• Wording review done
• Code review done
• Tests were added if useful/possible
• Reviewed for breaking changes
• Developer changelog updated if needed
• Documentation added if needed
• Existing documentation updated if needed

[caddoo]

I've tested the new addition, and it works as expected nice!

My main concern is test coverage. It looks like the tests focus on failure cases for invalid dates, which is good, and I appreciate the comprehensive testing of the dry-run behavior. However, there isn’t a test that verifies whether the command actually performs the intended action when executed successfully.

I don’t think it's necessary to test every possible path like with the dry run, but at least one test should be added to confirm that the command correctly resets invalidations in a real scenario.

Let me know what you think