[infra] Integrating generation of W3C-ready review drafts into build pipeline

[sideshowbarker]

https://github.com/whatwg/dom/tree/review-drafts-w3c-additions has the W3C-ready review-draft output for the 2019-06 review draft of the DOM spec — and specifically in https://github.com/whatwg/dom/commit/be3bc514d6db2c158d450bbdcfae23d3b3d9c40f, the HTML source for the W3C additions, and the build script used for inserting those additions.

Related: https://github.com/whatwg/whatwg.org/tree/sideshowbarker/deploy.sh-w3c-additions has some temporary changes to the deploy.sh script that are necessary for generating the MDN annotations in output, until such as time as Bikeshed merges the MDN-annotation-support patch.

[domenic]

So here's my proposal for how we do this, largely based on my reading of what would make @annevk the most happy:

• Download https://dom.spec.whatwg.org/review-drafts/2019-06/ into a .html file that we check into the repo, as review-drafts/2019-06.html. Update the deploy script to prioritize .html files over .bs files when building/deploying review drafts. (1 commit)
• Use the scripts to modify review-drafts/2019-06.html to become a CR and send a pull request with the modifications. We can review and nitpick the diff as necessary. This lands as one commit, and the deploy script from the previous bullet auto-deploys it over our current RD.
• When the RD goes from CR to REC, repeat the previous bullet.