[MONDRIAN-2124]  Cell queries are not aggregated when ignored/un-matched columns are present

There's logic in AggregationManager.findAgg() which determines whether or not it's possible to omit the rollup when pulling data
from an aggregate table.  This is allowed, for example, if the granularity of the request matches the granularity of the agg table.
Formerly we were determining whether the granularity is the same  by looking at whether the bitkeys matched, and whether
the agg table was fully collapsed.  This left open the possibility that ignored or unused columns in the agg table could result in difft
 granularity.  Now we take the conservative stance that presence of any ignored column means that we have to rollup.
 Similary, for distinct-count measures, if an ignored or unused column is present, we now make the assumption that the agg table
 cannot be safely used.
Merge pull request #333 from mkambol/mondrian-2124

[MONDRIAN-2124]  Cell queries are not aggregated when ignored/un-matched...
[MONDRIAN-1061] - junit tests added

junit tests added to reproduce java.lang.StackOverflowError

	modified:   testsrc/main/mondrian/rolap/VirtualCubeTest.java
[MONDRIAN-1061] - java.lang.StackOverflowError resulting from recursive calculated member usage within virtual cube

fix added to avoid recursion loop

	modified:   src/main/mondrian/rolap/RolapCube.java
Merge pull request #351 from prakapenka/MONDRIAN-1061

MONDRIAN-1061 - java.lang.StackOverflowError resulting from recursive calculated member usage within virtual cube
[ENGOPS-533] Removed duplicate version prop

Doing test builds noticed 'dependency.pentaho-launcher.revision' was in here twice.
Release builds set this version to the current suite-release/nightly build version so use trunk-snapshot here.
[MONDRIAN-2109] Display a proper error message when a calculated member is used inside of ValidMeasure.