HV-1363 Remove redundant check in ConfiguredConstraint

- based on the usage of the method we cannot receive methods into it,
hence the check can be removed. And also the method can be named more
specific to represent what it is really should be doing.

Author: marko-bekhta

engine/src/main/java/org/hibernate/validator/internal/cfg/context/ConfiguredConstraint.java

@@ -56,11 +56,11 @@ static <A extends Annotation> ConfiguredConstraint<A> forType(ConstraintDef<?, A
 		return new ConfiguredConstraint<>( constraint, ConstraintLocation.forClass( beanType ), ElementType.TYPE );
 	}
 
-	static <A extends Annotation> ConfiguredConstraint<A> forProperty(ConstraintDef<?, A> constraint, Property property) {
+	static <A extends Annotation> ConfiguredConstraint<A> forFieldProperty(ConstraintDef<?, A> constraint, Property property) {
 		return new ConfiguredConstraint<>(
 				constraint,
 				ConstraintLocation.forProperty( property ),
-				property instanceof JavaBeanField ? ElementType.FIELD : ElementType.METHOD
+				ElementType.FIELD
 		);
 	}
 

engine/src/main/java/org/hibernate/validator/internal/cfg/context/PropertyConstraintMappingContextImpl.java

@@ -59,7 +59,7 @@ protected PropertyConstraintMappingContextImpl getThis() {
 	public PropertyConstraintMappingContext constraint(ConstraintDef<?, ?> definition) {
 		if ( property instanceof JavaBeanField ) {
 			super.addConstraint(
-					ConfiguredConstraint.forProperty(
+					ConfiguredConstraint.forFieldProperty(
 							definition, property
 					)
 			);