Add recover-status-timestamps command

[HebaruSan]

Some mods have null timestamps, usually because they were only ever inflated by the legacy webhooks, which did not update the status file. This is inconvenient for changes that use these timestamps, such as #96.

Now a new recover-status-timestamps command is added that sets each null ModStatus.last_indexed to the timestamp of the newest commit in CKAN-meta for that module. This command is a one-off script and so it is not configured to run automatically; we would need to run it once on the server manually to backfill these timestamps.

[DasSkelett]

I'm not happy with "cluttering" the cli.py with one-offs. But tbh, I don't have an alternative in mind either.
Maybe this could benefit from #92? We could put it at least in a separate file then.

[HebaruSan]

Agreed, but we do already have a one-off in there (the job that copied the old status.json to ModStatus), so I think it's sound in principle:

NetKAN-Infra/netkan/netkan/cli.py

Lines 152 to 159 in 1eed50c

	@click.command()
	@click.argument('filename')
	def restore_status(filename):
	click.echo(
	'To keep within free tier rate limits, this could take some time'
	)
	ModStatus.restore_status(filename)
	click.echo('Done!')

One possible advantage of #92 here is that we could put normal commands and one-off commands in separate folders. netkan/netkan/cli vs netkan/netkan/cli/scripts e.g.

[techman83]

One possible advantage of #92 here is that we could put normal commands and one-off commands in separate folders. netkan/netkan/cli vs netkan/netkan/cli/scripts e.g.

We could also use a different python entrypoint, say admin_cli.py

netkan_admin=netkan.admin_cli:admin

[techman83]

LGTM, I'll merge this and give it a run. I've taken a sanity copy of the status dump just in case.