Rudder

We have the full story:

- 1/ when first deleted from editor, data in LDAP (active technique) were not deleted. There should have been an error message or deletion should have been interrupted,
- 2/ the fact that restarting rudder-jetty create back the technique in editor let think that technique files are not correctly deleted or that deletion is not correctly commit in git,
- 3/ when trying to create back technique in editor, there's that error:

Could not create ncf technique <- An error occured during technique update after files were created for ncf Technique Package Absent <- Unexpected: Accumulated: Error when automatically activating technique 'Package_Absent'; cause was: Consistancy: Can not add a technique with id 'Package_Absent' in user library. active technique 'activeTechniqueId=cfc7f8d8-3fff-4935-9874-e71890e7fd9e,techniqueCategoryId=ncf_techniques,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration}' is already defined with such a reference technique.

- 4/ ... but the technique is still created in editor

- 5/ if we delete it (again) from editor, then go to 'settings > active tree', we see the technique. Clicking on it leads to message:

Can not find dependencies. Can not build tree of dependencies for Technique ActiveTechniqueId(cfc7f8d8-3fff-4935-9874-e71890e7fd9e)

(which is OK, since we deleted at least parts of files)

- 6/ deleting technique from 'active tree' screen finally clean the state.

Now we can create back the technique and there's no message anymore.

Correction:
For 1/: We need to make sure to first delete data in base, then in fs/git and show related errors to user, with actionnable hint about what he can do. It will be handled in that ticket.

In 3/: we need to correct error message (s/ncf technique/technique/, give user hint that he can delete corresponding active technique in "settings > active tree" => #18016

For 4/: we should really NOT display a thing in editor if we just told user that it failed => #18016