Create a cache-busting mechanism for Calisphere repository data

[amywieliczka]

The Calisphere application caches repository data from the registry: https://github.com/ucldc/public_interface/blob/main/calisphere/registry_data.py on application start up: https://github.com/ucldc/public_interface/blob/main/calisphere/apps.py

For Calisphere running in ElasticBeanstalk, this means that updates to repository data require the underlying ec2 instances to cycle out before Calisphere reflects changes to the underlying repository data. I suspect this is why it took from Friday Oct 17th through Tuesday Oct 21st to see an update to the email address for this institution: https://calisphere.org/institution/132/collections/ (reported by Gabriela)