Initial script to compare cache list against topology (SOFTWARE-3470)

[edquist]

Per SOFTWARE-3470, ideally we'll incorporate this into CI checks, and perhaps even auto-generate OASIS StashCache configs.

Current script output

$ ./diff_cache_configs.py 
Missing items from osgstorage.org.conf (to add)
 - fiona-r-uva.vlan7.uvalight.net:8000
 - hcc-stash.unl.edu:8000
 - helm-cache1.osgdev.chtc.io:8000
 - sc-cache.chtc.wisc.edu:8000
 - stash.farm.particle.cz:8000
 - stashcache.grid.uchicago.edu:8000
 - stashcache.gwave.ics.psu.edu:8000
 - stashcache.jinr.ru:8000
 - stashcache.uchicago.slateci.net:8000

Extra items in osgstorage.org.conf (to remove)
 - fiona.uvalight.net:8000

Missing items from ligo.osgstorage.org.conf (to add)
 - dtn2-daejeon.kreonet.net:8443
 - fiona-r-uva.vlan7.uvalight.net:8443
 - hcc-stash.unl.edu:8443
 - stashcache.gravity.cf.ac.uk:8443
 - stashcache.gwave.ics.psu.edu:8443
 - stashcache.t2.ucsd.edu:8443

Extra items in ligo.osgstorage.org.conf (to remove)
 - dtn2-daejeon.kreonet.net:8444
 - fiona.uvalight.net:8444
 - stashcache.gravity.cf.ac.uk:8444
 - stashcache.t2.ucsd.edu:8444
 - xrootd-local.unl.edu:1094

[DrDaveD]

@edquist I am thinking that it may work better for this check to be part of a topology CI check instead of in config-repo. Whenever there's a change to the list of servers made, it has to be done on one side first, and so there will be a mismatch for a period of time. I'm thinking that it would be best for that change to be made here first, then have topology fail a CI check if anybody changes that list of servers and it doesn't match what is here.

[edquist]

Ok, per discussion in SOFTWARE-3470, we're going to do the CI checks via GHA cron in the osg topology repo rather than here.

See: https://github.com/opensciencegrid/topology/pull/2676