Adjust post-beetmover-dummy's tasks and deps.
- Fennec doesn't have beetmover-repackage or beetmover-checksums,
so add `beetmover` to the post-beetmover-dummy kind-dependencies.
- Add a fennec-promote post-beetmover-dummy job.
- Remove the extraneous -ship post-beetmover-dummy jobs. Once we
removed the assumption that dummy jobs had to be in the same phase,
these became redundant.
In testing, this looks good. For the next step, we may want to split
these dummy tasks up by `build_platform`. Then downstream tasks could
then optionally filter their dummy deps by `build_platform`; this
would allow for certain platforms to proceed on to the next steps
sooner, rather than wait for the slowest platform to finish.
I also suspect we don't need post-beetmover-checksums-dummy at all;
it's redundant.
MozReview-Commit-ID: EeHjwTQnVB1
--HG--
extra : rebase_source : 812288cf083499d38e3e47a203c43163afd8e2a5
extra : source : e78626133e88e124922a43b5af7ebfd5e5325360
This allows us to funnel large numbers of tasks down to avoid hitting
MAX_DEPENDENCIES. I avoided using a morph here because we might break
certain cot assumptions.
MozReview-Commit-ID: BIILM9O6CI4
--HG--
extra : rebase_source : 48bd11e8b6f25887671aafec23b2a27aad98b9d1
extra : histedit_source : 7bd193e12043272ed4ea6059260ed7abfca4d1d1
