There is a problem when converting a domain object to an array.
in the case of a combination of several OR operators, the retroconversion into an array
from the domain object is not equal to the original array used for initialization.
The problem can be related to the initialization of the domain object or to the
conversion to an array, but in any case, it is out of this PR scope.
The humanDomain needs an array domain, which mean that the conversion and the
retro-conversion are useless in this case.
Before this patch, when searching with the "equals to" operator in any
x2many field, the searched parameter was always `undefined`.
The problem was that the underlying field manager implementation was
treating those fields as x2many, while the widget used was the `one2many`
one.
This patch simply mocks the underlying fake record to make think that
any relational field is always a `one2many`. This sets all pieces in
place and makes the field manager work as expected, and thus you can
search as expected too.
* Complete migration to v11
* Refactor to use the new v11 decoupled widgets system
* Advanced search is now a high-level feature from the filters menu; it simplifies code a lot, and the UX is even better
* Split README system
* Add fun to ROADMAP
* Addon is renamed to web_advanced_search, since it enhaces the searching experience for all kind of fields now
