New way, how Mtest.py gets to know about conditionals set by configure:
New way, how Mtest.py gets to know about conditionals
set by configure:

Mtest.py used to get the conditionals as set by the configure
of MonetDB (Common) at compile time of MonetDB (Common);
thus, these were not necessarily the correct values for other
packages, and conditionals that are only set for certain packages
but not for MonetDB were not known to Mtest.py at all.

Now, Mtest.py uses the new "--conds" option of the packages'
"monetdb-PKG-config" scripts, and hence gets the very package's
conditionals values dynamically at runtime.

zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb