chore: update the Foundation to v8.19.0

[owenvoke]

I noticed that Laravel core now includes a schedule:list command. Currently in the framework, we have a schedule-list component. Not sure how we want to handle this situation. 🤔

@nunomaduro (and @billysmithers as you opened the original PR with this component), what are your thoughts on this? It looks like the package has more functionality than the one included in core.

[billysmithers]

@owenvoke Thanks for considering me in the discussion. I have no issue in moving to the Laravel core command, as it is then something maintained at that level. However am happy to see what other people think especially if it means losing functionality that users of the Zero framework rely on.

[nunomaduro]

The "schedule-list" component is an opt-in? If yes, maybe we leave it?

[billysmithers]

@nunomaduro As far as I know it is an opt-in. @owenvoke would there be conflicts with the core command if we left the component in place, I think they share the same signature?

[nunomaduro]

I think the component will override the existing one. So it's fine.

[owenvoke]

Ah, if it overrides the one from core, then that's fine. I'll have a quick test to double check and then release this. 👌🏻 Cheers both of you for your input!

[owenvoke]

Ah, just remembered it doesn't matter as the command isn't registered in Laravel Zero's framework. 👍🏻 Merging.