The current .github/workflows/gpkg-to-pgdump.yml has several issues to be resolved.

1. The steps for "opendrr-boundaries.dump-generation from GeoPackage files" take quite a long time (about 40 minutes) and not strictly necessary because it is essentially identical to opendrr-boundaries.sql that Will uploads routinely anyway. Let's move these steps to a separate workflow file.

2. Revert gpkg-to-pgdump: Disable keep-cache-fresh cron schedule #29 and restore Git LFS cache refresher workflow in a separate "cache-refresher.yml" file, so in case it gets deactivated by GitHub for inactivity over 60 days, the normal workflows won't be deactivated too.

3. Use concurrency to run a single job at a time. There was problem with multiple runs uploading to B2 or S3 at the same time resulting in failure. See:

   • GitHub Actions: Limit workflow run or job concurrency | GitHub Changelog (new in 2021-04-19)
   • Using concurrency - GitHub Docs
   • Workflow syntax for GitHub Actions - GitHub Docs
   • GitHub Actions: Concurrency - YouTube
   • Preventing concurrent GitHub Actions
   • Recent hiccups with concurrency that has since been resolved?
     • Breaking change to concurrency group syntax? - Code to Cloud / GitHub Actions - GitHub Community
     • concurrency with properties now causes "syntax error" · Issue #1532 · actions/runner
   • Before GitHub's concurrency support came into being: actions-mutex · Actions · GitHub Marketplace

4. Rethink whether to trigger the workflow(s) for pushes to master, and whether to do something for pull requests.

5. Add manual workflow_dispatch trigger to allow uploading of release asset files to existing release. Thanks to @DamonU2 for pioneering this feature in Action fix earthquake-scenarios#19

   • See if the release version can be specified manually as tag_name with softprops/action-gh-release@v1

6. See also Split opendrr-boundaries.{sql,dump} into 2GB chunks before uploading as release assets #34, to be dealt with probably in the same pull request.