As pointed out in T389863#10671903, the 8 templates that Flow creates during MW installation can make other tests slower: not only the creation of the templates themselves, but also any jobs associated with those pages. This wouldn't necessarily be bad per se, but it becomes problematic when these templates are also not used in any tests, so they slow things down for nothing. So, my proposal is that we gate the template creation behind a check to see if we're running inside quibble (MW_QUIBBLE_CI).