Converter ignores disabled status of system user

kpauls, IMHO the content-package-2-fm-converter should spot if system-users are marked as disabled (i.e. if they have rep:disabled property set and should reflect that in the set of repo-init statements generated upon conversion.

While this is probably not a very common scenario it still has a significant impact as disabled system users are not allowed in sling service user mappings (and should allowed to login).

the fix should be straight forward:

• test if rep:disabled exists with users/system-users
• extend User/SystemUser to allow to have a 'disable-reason' set (groups can't be disabled)
• when generating repo-init statements in DefaultAclManager add an additional DisableServiceUser operation if a user is marked as disabled.