Give priors a unique file name on modification?

[damonbayer]

https://github.com/CDCgov/pyrenew-hew/commits/main/pipelines/priors/prod_priors.py

We have made mild changes to these priors since first implementing them. Of course, the version history is tracked in git, but, I think it would be easier to reproduce old fits if we created a new file each time we changed the priors. Otherwise, we have to somehow reconstruct the priors by parsing the git history.

What do you think @dylanhmorris?

[dylanhmorris]

As I mentioned here, I think releases are the way to go for tagging versions of a model that go into production without cluttering up the latest version of the repo