handle non development seeds

[sean-dickinson]

What

• Updates the seeds so that they can run on staging/production
• Adds testing the seeds back to the ci script now that seeds run in test correctly

Why

• I initially set up the seeds only expecting to run the in development, however I realized there is some data that should always be present in deployed environments as well that we don't support crud for as is it system data that should always be present and not editable.

Open Questions

• Something I always wonder about is if we should take the time to use a secret for this admin password via this seeder now that it is for staging/production? Or if we should just leave it as is, and then we add a run book for production to remove the seeded admin user once it is used to create the real users?