Move configuration to the dabase

Each board should grab it's configuration from the server and it should be updated every data-send cycle.
Passwords should be stored securely with encrypted form and boards should have their private key to decode them into usable formats.
Provide frontend support for changing this data

No files, tests, or entry points are named. Start by mapping how boards receive configuration, how the server stores and updates it during each data-send cycle, and where the frontend manages this data. Done should include server-backed board configuration, secure password handling with board-specific decoding keys, and frontend support for changing the configuration.

Written by the indexing model from the issue text.