Populate the production database with valid resources

[amcewen]

Now that #16 and #17 are done we've got a basic site running. When you try to select a resource it returns an error, which (I think) is because there's nothing in the production database.

We should work out how we'll populate it, and then put the right info into it.

[amcewen]

Once we know how changes to the database are managed, we should make sure the Github Action created in #48 runs any relevant updates to the database when new versions are deployed.

[amcewen]

The database seeds already set up for the production environment (a copy of the development ones) seem a reasonable start. So on the production server I ran docker-compose exec api npx knex seed:run --env production which has populated it with the initial data 🎉

We'll need a better system to manage any updates in future, but this is okay for now. #20 might give us an answer for the ongoing changes... and I've spun the running the database migrations during deploy out as #56