Cloud DB Keep Alive

[thenickedwards]

The cloud database supporting the deployed site is being paused due to inactivity (per Supabase policies). Ideally we can automate a fix which will regularly touch the database, without manipulating visible data, and keep the project active--this is particularly crucial for tables which are effectively archival/historical (i.e. past seasons) and during the offseason when updates are less frequent.

[thenickedwards]

Thankfully we live in a world where I'm not the first person to encounter this issue. While that person is charging for their solution (more power to you, get that bag!), during my search I stumbled upon supabase-pause-prevention.

This project re-directed me to the updated Python version supabase-inactive-fix which I have forked and refactored to keep the Duels Mapping](https://github.com/thenickedwards/duels_mapping/) database alive.

Introducing supabase-watchdog 🐶

This repo will use GitHub Actions to ping our database twice a week and add a new record to a table we're not using. If there's over a certain number of records, one is deleted so we don't end up with some big table that's going to incur a storage charge. I've added the table to DM's database setup as well. I'm debating whether to have it as a git submodule in the DM repo or leave it stand alone. This little setup should ensure the project isn't paused, the deployed app remains active and available, and the project is not deleted by Supabase.