SettingsDAO should be split in two part app settings and server specifc settings

Today we are using server ID 0 to store the app settings. We should have a dedicated model for the app settings and one other for the server.

This will also need migration from the single table to two within room to not loose any settings.

Start by locating SettingsDAO and the Room entities and tables it uses. Trace how server ID 0 currently stores app settings, then identify the migration path that separates app settings from server-specific settings. Done means both models exist and the migration preserves all existing settings without loss.

Written by the indexing model from the issue text.