Related to nemo-ce:22 [feature request] Trainings: dependent tools.

I open this issue to follow up on the development of new "dependent tool" feature.

Rationale

In some lab/facilities, some "primary" tools might have "dependent/ancillary" tools which are used for part of the process (e.g. a workstation used to setup processes for many different tools).
This requires additional actions, which might be simplified/automated by this feature. Some examples are:

1. When creating a reservation on primary tool, asking the user to (optionally) create additional reservation for each "dependent" tool.
2. When moving/deleting(/resizing) a reservation for primary tool, also move/delete(/ask to resize?) the dependent tool.
3. When engaging/disengaging a primary tool, ask user to (optionally) engage/disengage the primary tool.
4. When training/qualifying a user on a primary tool, automatically (or optionally?) train/qualify the same user on dependent tool.
5. (optional) add the option when scheduling an outage on dependent tool, so outages can be created for primary tools if requested. Not sure if also vice-versa.
6. (nemo-ce only): when creating a training event for a primary tool, ask to create a simple reservation linked to the training event. Moving/resize/delete training shall also act on linked reservation.

Implementation notes (from linked issue)

• In Tool, add dependent tools many to many field
• When making a reservation, ask the user if they would like to make reservations on the dependent tools as well, with checkboxes/additional start/end fields for each dependent tool.
• Then we would have to go through the regular reservation process for each dependent tool that was checked, in case there are reservation questions, configuration settings etc (or display them all together but I am not sure that'll be easier... it's probably unlikely there will be dependent tools with configuration, but we have to account for it). This could be done by saving the dependent tool ids and start/end times, and when the first reservation is successful (keep that reservation id in case of issues), submit the second one as if the user actually clicked on it to schedule it. If there are issues with one of the reservations, use that reservation id that was kept to cancel it.

Feel free to edit/correct description