MODE-2290 Corrected use of mixin aliases in determining whether indexes are applicable

When an alias is used in a query, there is a constraint that specifies the allowed values for the 'jcr:primaryType' or 'jcr:mixinTypes' properties. (This constraint is added during the planning/optimization phase, and is based upon whether the selected node type is a mixin.)

The logic used in the IndexCalculator was only looking for constraints on 'jcr:primaryType', and thus any alias on a type that was a mixin type would not apply to any indexes. Changing the logic to also look at the 'jcr:mixinTypes' in the property value of the constraint fixes the problem.
MODE-2290 Refactored the local index provider tests

Refactored the synchronous and asynchronous local index provider tests so that we don't have to run very many of the tests asynchronously. Really, we just need async tests to verify that the indexes are indeed updated asynchronously and that queries will be able to use them.
MODE-2304 Removed the unused @SuppressWarnings annotation

Fixed the compiler warning.
Merge pull request #1276 from rhauch/mode-2290

MODE-2290 Corrected use of mixin aliases in determining whether indexes are applicable