Update the configuration on an addon subscription

This is also the only place an addon's data permissions (e.g. access to client documents) can currently be changed, so it doubles as the "permissions changed" audit event until a dedicated permissions model exists. Config holds credentials and account ids alongside anything permission-like, with nothing marking which is which, so the entry is tagged and titled as a configuration change rather than claiming a permission changed when someone only corrected a username.