CI: scheduled pipeline report misleading when deployment did not run

@cristian.manda noticed that the scheduled pipeline report is misleading when child deployment pipelines aren't started because of a failure in their parent pipeline

example here:

https://gitlab.com/sylva-projects/sylva-core/-/pipelines/2663174619

image

We could improve this by having the report tool:

  • check the scheduled pipelines board to see what was the last parent pipelines that were started
  • in those, find the deployment pipelines that did not run because of other failures
  • include information about them in reports.json
  • in the HTML report, display those as "Didn't start"