Remove secrets from repo

One example is the admin password in the users table seeder. Instead of having a hardcoded password, it should be generated randomly when the seeder is run and the password can be show in the console.

Start with the users table seeder mentioned in the issue and inspect how the admin password is currently defined. Run the seeder to confirm its current behavior, then verify that the password is generated at runtime, is no longer hardcoded, and is shown in the console.

Written by the indexing model from the issue text.