allow dev npm script to run prisma db migration

[nickvisut]

Currently, prisma schema changes cause local dev to error out (usually referring to something like a missing field) unless a prisma migration is executed. One way around this is to manually run the build script after seeing said errors.

As a potential way to automate this and improve DX, this issue proposes to run the migration as part of the dev script.

• Optionally, it can first test if a migration needs to be done before actually running the migration task to save developer time
  • this test already exists as the npm script check-migrate, which return a non-empty output if a migration needs to be done; this can be incorporated into logic to either migrate or not instead of always attempting a migration

[nickvisut]

Noting here that there is already an issue that appears to address this, albeit w/a different approach. Look into possibly consolidating the two.

Related to #80