Enhance object checks: types user, adapter, group common.name only string

[Apollon77]

Currently the "common.name" property can be a strin gor an object (with localized strings). Currently we accept both types for all objects.

In fact the objects of types user, adapter and group that are created by users should never have a name object property. Exception are the user and group objects created by the js-controller io-package (so disable the strict-checks when creating them)

[foxriver76]

Curiosity: What type adapter objects are user created?

[Apollon77]

Right, normally none :-)

[foxriver76]

for type adapter it always needs to be a string according to our schema.

[Apollon77]

for type adapter it always needs to be a string according to our schema.

exactly

[foxriver76]

Existing problem: If someone adds a user to a group, or make changes on user/group, admin will rewrite the name as it is and only write the string name if really the name has changed. Thus, the warning gets generated if a user makes such a change.

[foxriver76]

For adapter this is not a problem

[foxriver76]

See #1645

[foxriver76]

So how we want to proceed here in the long run? allow both or make adjustments in admin so that the name will be set according to the configured language.