Run CI against blab/veme-2022 and zika-tutorial

[jameshadfield]

Currently we have (the extremely helpful) pathogen-repo-ci CI action (although it confusingly doesn't use the reusable workflow of the same name). This helps ensure changes to Augur don't inadvertently break our ~core pathogen builds. We should do the same for the VEME tutorial repo and the zika-tutorial workflow, which are often external users' first interactions with Nextstrain/Augur. The latter is essentially our quickstart guide.

Adding zika-tutorial to our CI should be easy.

Adding the VEME tutorial will be harder because it does not use a Snakefile. Rather than add one, we could extract the salient commands programatically from the README. Similarly to how individual build repos run their own CI (often using the reusable pathogen-repo-ci workflow), VEME should do the same.

This would have caught the regression patched by blab/veme-2022@f14bbe6.