right now, skapi loads the set of OAuth2 clients (client-id and client-secret) from the sako database when one creates a skapi.Server value.

the underlying oauth2 server and its underlying client store aren't updated when one adds or removes OAuth2 clients.

perhaps modifying the clients list should be done through a set of skapi endpoints (instead of directly going through the sako database as is done currently), so the internal consistency of skapi.Server is preserved. (and we wouldn't have to expose skapi.Server.ReloadOauthClients)