refactor profileManager to use KV storage for config/auth

this falls back to the DB, it also still creates stub entries in the Profiles table since we use them and they're very handy there administratively just for the pid+service+created timestamps

it doesn't require a tricky migration (but one should be written later to ensure everything is moved), it reads from both, just writes to the KV store (riak)