This prevents adding duplicate principals, but since this code doesn't track the key names, this use case would break:
1. Add principal "a@a" with the key name "foo"
2. Add principal "a@a" with the key name "bar"
3. Remove the key named "foo"
4. The key named "bar" still exists in mongo, but the associated principal no longer exists in .k5login