Ignore Nextclade cache on new Nextclade version or dataset version

[joverlee521]

We've had a history of caching issues (#456, #392) come up whenever there's a new release of Nextclade or SARS-CoV-2 Nextclade dataset and we forget to manually upload the *.renew files to trigger the full re-run.

The workflow should automatically ignore the Nextclade cache if it encounters a new Nextclade version or dataset version.

[joverlee521]

Also prompted by discussion in blab/forecasting project to surface Nextclade/dataset version in the sequence counts generated by forecasts-ncov/ingest

[corneliusroemer]

Good idea, yes.

Shouldn't be hard to set renew files programmatically based on equality or not of the columns in the existing files with the current software and dataset version!