Using `timestep_collect` tasks for void cells instead of doing them in `engine_step` collectively

As the title says, voids now get a task_type_collect task at the top level. This removes the cell_has_task void-specific logic. Important points:

• The void->timestep_collect is unlocked by the zoom->timestep_collect to ensure everything has been updated at the zoom top level before the void cell tree is traversed.
• The void->timestep_collect uses its own bespoke runner function that ignores the super check because we want to go the whole way past the super level to the void leaves (top level zoom cells) and ignores the hmaxs. This is because void cells don't have timestep tasks (and don't need to) and they will never need to know about the smoothing lengths respectively.
• This has been tested and runs with debugging checks on perfectly happily. It also doesn't appear to introduce any hold up due to the zoom -> void dependency.

src/zoom_region/zoom.h

@@ -28,6 +28,7 @@ struct swift_params;
 struct space;
 struct cell;
 struct engine;
+struct runner;
 
 /* Define a constant for the background task depth. */
 #define zoom_bkg_subdepth_diff_grav_default 4
@@ -60,5 +61,6 @@ void zoom_engine_make_self_gravity_tasks(struct space *s, struct engine *e);
 void zoom_engine_make_hierarchical_void_tasks(struct engine *e);
 
 /* Update the void cell gravity timesteps. */
-void zoom_void_timestep_collect(struct engine *e);
+void runner_zoom_do_void_timestep_collect(struct runner *r, struct cell *c,
+                                          const int timer);
 #endif /* SWIFT_ZOOM_H */