Periodically regenerate catalog mocks

[dcarley]

Acceptance criteria

Add a weekly CI job that:

1. Re-generates all of the mocks with just gen-data -f
2. Runs the integration tests
3. Alerts us of any failures

Why

It will make us aware of breaking changes like:

• https://github.com/flox/flox/issues/2034

Notes

The frequency can be adjusted at a later date if needed, e.g. triggering from changes to the flox/catalog-server repo.

We don't (currently) want to raise PRs for non-breaking changes because they'll generate lots of noise.

[mkenigs]

• We should make sure the automation to notify us of schema changes is working
• When we get schema changes, we need to make sure we re-generate the mocks
• We can re-evaluate if we need to trigger something periodically after schema changes become less frequent

[dcarley]

We should make sure the automation to notify us of schema changes is working

Raised https://github.com/flox/catalog-server/pull/167 which should fix that part.

[dcarley]

https://github.com/flox/catalog-server/issues/193 and https://github.com/flox/catalog-server/pull/226 should be sufficient.