Provide clear expecations about the time commitment to new teams

[PeterJCLaw]

We've heard from a number of new teams that they've underestimated the time commitment or that they've had clashes with other events in the week. Obviously we don't want to scare potential teams off, but some general guidance is probably a good idea.

Looking at our docs for new teams (in particular https://studentrobotics.org/compete/ and https://studentrobotics.org/docs/robots_101/team_supervisor) there's nothing much there which says how much time teams should expect to spend on their robots. It would be great if we could provide some more guidance.

Part of this probably involves polling a few teams to understand better how much time they put in, though we should also emphasise that this does vary quite a lot. We know that some teams meet once a week for a couple of hours, while other teams meet twice a week for longer than that. Partly this will also depend on how much they want to get done outside that time -- perhaps on their own evenings/weekends or by coming to Tech Days.

The places we should put this are probably the same places I've mentioned above (the compete page and 101 article for team supervisors), though there may be other places.

There might be overlap here with #1224, though likely this task can be done without that one.

[PeterJCLaw]

https://studentrobotics.org/docs/robots_101/team_supervisor has more detail now (since srobo/docs#608) and both that and the new https://studentrobotics.org/docs/robots_101/programme_structure page were included in our messaging & sign up form for SR2025. I'm happy that that covers this fairly well, though we should get feedback on this as part of getting feedback for SR2025.