Shema update part 2

Shema update part 1

Add modelisation of life cycle tasks + related schema updates

Add last exec to tasks.

Adds BCC

Adds subnodes attachments during first creation.
Apply or update has to be fixed.

Allows the creation of repeatable tasks as well as defining scope of new or old members

Adds possibility to add source when creating a snapshot.

Signed-off-by: Benoit Mortier <benoit.mortier@fusiondirectory.org>

Adds new schema numbering for tasks, mail template,
plugin manager, task dashboard and relateds configuration.

Updates schema for core and pluginManager.

Removes unrequired attributes from the class as well as from the
schema.

Signed-off-by: Benoit Mortier <benoit.mortier@fusiondirectory.org>

Signed-off-by: Benoit Mortier <benoit.mortier@fusiondirectory.org>

Includes tasks config backend.
Allows spam protection management.

Mail Tasks can now select the proper mail object type
required, making selection of differents emails type possible.

Granular tasks are not updated properly.
Erros messages are now exact and not generic.

Updates for dashboard - version 0.3

Adding some features to create dynamically tasks
dashboard. Allowing tasks mail to create granular objects.

Adds proper time schedule with proper attribute.
Change of schema to adapt to this change.

Add sender emails and fixes typo in ldap schema.

Mail retrieval from DN put in LDAP.
Commit to fix in order to save attribute in ldap.

Each cells of tasks management report informations.
Not proper ones yet, but it is a start.

Removes requirement for a name within Task Mail name

Add users selection for mail task as well as schedule within
generic page of tasks creation.

Adds management required columns, back processing still has to be
developped

Adds the first configuration page of Macro.

Mail list will be implemented within Task object

Add invitations fields and verifications of mail list imported.
Adapts the core-fd.schema.

Adds user reminder capability as well as adding conflict between
user recovery and itself. Disallowing the activation of the tab.

Adds User Recovery TAB and search ldap method to make sure
only one User Recovery Mail template can exists.

Basic mail template object created with required fields.
Next steps is file attachment processing.

issue #6152

issue #6152

issue #6152

issue #6152

This is an attempt at putting restored object through FD open/save cycle
 to make sure they save without error and trigger any hook that may look
 for changes.
Also store object type in the snapshot LDAP node, even if it is unused
 at the moment.

issue #5715

Resolve "Core-fd.schema as gosa in description when its fd attributes"

Closes #5707

See merge request !29

(cherry picked from commit 99905828)

cadd7c24  fix(schema): Core-fd.schema as gosa in description when its fd attributes

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>