SPIKE: Add test data to dev deployments TIMEBOX = 3 days

**Describe the task**
To avoid data bugs, we should include test data in dev deployments.

**Acceptance Criteria**
- [ ] Identify a useful subset of test data
- [ ] ~~A dev deployment should include test data when spun up~~ A postgres service container could run in a Github action pipeline that runs our migrations, and then a series of data related tests could run against it: https://docs.github.com/en/actions/use-cases-and-examples/using-containerized-services/creating-postgresql-service-containers

**Additional context**
- Some approaches
- Create a migration that only runs in dev env to add test data (preferred since this leverages existing infra and easier to keep in line with database schemas)
- Create a static sql dump that gets imported in dev deployment crunchydb cluster

Start by reviewing the existing database migrations and the GitHub Actions PostgreSQL service-container documentation linked in the issue. Compare the dev-only migration and static SQL dump approaches, then define a useful test-data subset and confirm that migrations and data-related tests run successfully against the service container.

Written by the indexing model from the issue text.