Investigate removing release-notes cron entries from healthz

[janbrasna]

Description

Release Notes are no longer served from wmo. The cron endpoint should not list that job.

---

Success Criteria

• No leftovers esp. if otherwise unused
• Remove from configs if no longer run

[janbrasna]

Since #16577 the release-notes app is gone, incl. configs and git processing update management command, effectively leaving its https://www-dev.allizom.org/healthz-cron/ entry now frozen in time. To not lead to confusion that the release-notes job is stuck not updating (as this now runs on springfield), is it feasible to remove it now?

I'm not sure if there's another place that would actually clone the repo or keep its .git history, but the thing that feeds the healthz-cron is probably this django db model:

bedrock/bedrock/utils/models.py

Lines 12 to 17 in af49d1b

	class GitRepoState(models.Model):
	repo_name = models.CharField(max_length=200, blank=True)
	repo_url = models.CharField(max_length=200, blank=True)
	repo_id = models.CharField(max_length=100, db_index=True, unique=True)
	latest_ref = models.CharField(max_length=100)
	latest_ref_timestamp = models.IntegerField(default=0)

Is that clickops to remove the entry, or some other strategy via code?

[stevejalim]

Thanks @janbrasna - this came up recently as a point of confusion, so yeah, removing the entry from wmo is a good call.

Is this something you're interested in doing? If not I'll get it in the grab-bag for someone to pick up

[janbrasna]

I was not able to find where the individual repos pulled get bootstrapped to cache the timestamps et al. (and thus how to revert the process to un–bootstrap no longer used ones cleanly) — isn't that now just an unused row in the db table that can be e.g. removed in Django admin?