Routes refactor #18
Description
I'd like to refactor our web routes for better separation of concerns and logical consistency. We previously had profile, peers and messages as top-level routes but I think a forward-looking strategy is to move them under a /ssb route. That will allow us to neatly support other protocols in the future (for example, we could add /p2panda and then have /p2panda/profile etc.). Most of the other routes then end up being grouped into /settings and /status.
What do you think of the structure I've outlined?
Top-level Routes
/
/help
/scuttlebutt
/settings
/status
Scuttlebutt
/scuttlebutt/profile
/scuttlebutt/peers
/scuttlebutt/messages
Settings
/settings/network
/settings/network/ap/activate
/settings/network/dns
/settings/network/wifi
/settings/network/wifi/activate
/settings/network/wifi/add
/settings/network/wifi/connect
/settings/network/wifi/disconnect
/settings/network/wifi/forget
/settings/network/wifi/modify
/settings/network/wifi/usage
/settings/network/wifi/usage/reset
/settings/admin
/settings/admin/change_password
/settings/admin/reset_password
/settings/admin/send_password_reset
/settings/admin/power
/settings/admin/power/reboot
/settings/admin/power/shutdown
/settings/scuttlebutt
Status
/status/config
/status/device
/status/display
/status/dns
/status/network
/status/scuttlebutt