Is your feature request related to a problem? Please describe.

When a user starts Jam with npm start as described in "Connecting to a local instance", Jam will start in development mode and debug features are enabled, e.g. "skipping seed verification" or "insecure scheduler options".

Describe the solution you'd like
Instead of adapting the documentation or changing the mechanism for mainnet users, Jam should by default use "mainnet" settings and developers should change their way of starting Jam to enable debug features. This can be done by switching from starting Jam locally with npm start to e.g. npm run dev:start.