Fall back to implicit joins in this case.

We'd have to implement the collapsing of inner-joins contained inside other
inner-joins based on similar aliases, and consolidate their join conditions, before
allowing table aliases with explicit joins.

This commit reverts:
 631cab2b
 93cf49e4

...while attempting to build the ColumnMap.

This makes sure that buildSQLQuery() works even if no actual query is present.

Fix skin priority so it can be used in projects. Set it to 10.0 in a similar way as other "style" ones like ODT / ODS.

Otherwise they can not lookup(traverse) the utility.

This needs to be reverted after fixing either ZSQLCatalog or DomainTool to work
without it.

Try to be more defensive and run only if in proper page (otherwise it breaks some UI jQuery functions).

The previous test is based on the wrong usage of asContext at ConstraintMixin.applyOnAccessorHolder.
It was fixed at 7634c000.

Conflicts:
	product/ZSQLCatalog/SQLExpression.py

because it was wrongly removed at c7f1a35c
when replacing to specify the portal type with the rule reference.

Because they are testing newly added functions on new-simulation.

Don't even search for future trade phases.

Rules should now contain all predicates necessary for matching the right
simulation movements. Which they now can do since they all have "Predicate"
tabs now.

(partially revert 5c2c470f)

Use getTypeBasedMethod and unify handlers.

See Coding Crime Guideline.  http://www.erp5.org/GuidelinesForCodingCrimes
(thx nicolas)

The 'test' function seems to disappear in a few contexts. This should be fixed in Chameleon, but we work around it here for now

Commit 2f881b06 was a wrong fix because RLock
does not raise 'thread.error' like Lock (when releasing an unacquired lock).

(cf commit b709cc899fa17ed14569a96395ad2def3a545db4 of NEO project)