[7.x] Add a more generic minute schedule method

[browner12]

this PR was inspired by #33379

Rather than adding a method for every iteration of minute intervals, the thought is to have one method that accepts a parameter.

If there are any suggestions for a better method name, definitely open to them.

The only concern here is that we make it clear in the documentation how this actually works, specifically with values that are not factors of 60. For example, a value of */17 will run at the 0, 17, 34, and 51 minutes, and then start over again at zero on the next hour, so the expressions is not truly running every 17th minute.

If we can come up with a readable name, we could possibly deprecate and remove the existing function like ->everyFiveMinutes(), ->everyFifteenMinutes(), etc.

[driesvints]

Think the existing everyFiveMinutes, etc methods can stay but they can internally re-use your method?

[browner12]

Hmmm... the tradeoff is you're introducing another method to the call stack by doing that with the hope of keeping things DRY for better maintenance.

Normally I'd be on the DRY side of that argument, but it feels like you gain so little in this scenario, I might lean towards keeping the extra method call out of the call stack.

I'm fine either way on that, I'll leave that decision up to you guys.

[taylorotwell]

The odd numbers (like 17) make me want to avoid this.

[browner12]

what if we limit it to only factors of 60?

1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30, 60

if (60 % $minute !== 0) { 
    thrown new Exception();
}