Do not pre-validate restrictions

[kwin]

Oak takes care of that in
https://github.com/apache/jackrabbit-oak/blob/17281282fe82d0f0c4e86d0a42ecfb20bfe404e3/oak-core/src/main/java/org/apache/jackrabbit/oak/security/authorization/accesscontrol/ACL.java#L213 as soon as you try to apply those.
Otherwise you face exceptions when using restrictions only available at run-time in cloud (but not at build time).

This closes #854

[ggruianc]

@kwin there is another restrictions pre-validation in

accesscontroltool/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/validators/impl/AceBeanValidatorImpl.java

Lines 134 to 144 in 8fdc6ba

	final Set<String> allowedRestrictionNames = getSupportedRestrictions(aclManager);
	if (!allowedRestrictionNames.containsAll(restrictionNamesFromAceBean)) {
	restrictionNamesFromAceBean.removeAll(allowedRestrictionNames);
	valid = false;
	final String errorMessage = getBeanDescription(this.currentBeanCounter,
	tmpAceBean.getAuthorizableId())
	+ ", this repository doesn't support following restriction(s): "
	+ restrictionNamesFromAceBean;
	throw new InvalidRestrictionsException(errorMessage);
	}

[kwin]

@kwin there is another restrictions pre-validation in

Thanks, that validation should be removed now in 1c4b417

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 31%)

See analysis details on SonarQube Cloud

[ghenzler]

We should not just remove assertedException but then also the test case with the comment

[kwin]

For me this test shows that invalid restrictions do no longer lead to exceptions, therefore this is still helpful.