Rudder

So, what is happening is:

- when the value comes from inventory, we only have it in inventory LDAP branch ("ou=Accepted Node, ou=inventories, etc).
- the search for group does not look at that place, so it is "normal" to not find it with that search,
- the quicksearch does look at that place and find it,

BUT when we add a proprety, "inventory", it copy all properties to node, making it searchable.

Moreover, it seems that only the last inventory property is added.

Work in progess here: https://github.com/fanf/rudder/commit/766b309930b9519b016da49e5a137a9b7bdc8492

So, the copy bug was hidding the fact that the search is just plain missing on custom node properties from inventory.

So, the idea is to rework a little the way our search works to cleanly split search on node info apport from the one on inventories properties. It was not working eleganlty for NodeState in all case.

Basically, it means that each Criterion in DIT will be either an LDAP criterion (everything until now is such an LDAP criterion) or it will be a "node info criterion" (basically, a NodeInfo => Value => Boolean).

Then, we just post process these element correctly. We are already relying on NodeInfoService for that, we just have to extends a little the "getLDAPNodeInfo" method.

Finally, it will open-up the real of REAL JSON query (because, on node info, node properties are parsed JSON).

WIP here: https://github.com/fanf/rudder/commit/766b309930b9519b016da49e5a137a9b7bdc8492

Everything works for NodeState, now we need to build a NodeCriterion for NodeProperties and use it.