Add an attribute to enforce a strict index tag check ("selectionPolicy")

JCR Query which does not specify an INDEX() tag may eventually pick up the tagged index.

This is not an error, however this behaviour is not always desirable when a tagged index must only be used by a specific query which explicitly specify an index tag and be transparent to other queries which does not specify it.

If I understand correctly the check is done here

I propose to add a boolean parameter (strictTagCheck or sth similar) which enforces a strict check for the index tag - the idea is to mark such index as wrong in case query does not specify the index tag and an index definition contains a tag. I think this change is also a backward compatible as does not change the existing behaviour, but adds a new one.

N.B. Currently a workaround applied to set a high costPerExecution and costPerEntry in index definition has a negative side effect for the query to fall back to traverse and fail after it reads 100 000 nodes.

And, yes, it's an urgent issue