Schedule build errors should include the schedule in which the problem occurred when reporting problems #9510
Description
What problem does this solve or what need does it fill?
When errors are reported during schedule building, the schedule name is not included.
It would be helpful to be able to track down the exact source of the problem, especially since that information.
What solution would you like?
Currently:
2023-08-20T17:23:10.908705Z WARN bevy_ecs::schedule::schedule: 1 pairs of systems with conflicting data access have indeterminate execution order. Consider adding `before`, `after`, or `ambiguous_with` relationships between these:
-- update_action_state<PlayerAction> (in set Update) and ui_focus_system (in set Focus)
conflict on: ["bevy_ui::focus::Interaction"]
In the preamble to this reporting, we should report the schedule name if it is available.
Additional context
We won't always be able to report the schedule name, since this information is stored in Schedules, not on each individual Schedule. In theory I suppose we could change that though.