This PR was squashed before being merged into the 3.4 branch (closes#36627).Discussion----------[Validator] fix lazy property usage.| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Tickets       |Fix#36343| License       | MIT| Doc PR        |This attempts to fix a large regression introduced in#36343, which broke recursing values returned from `getter` Constraints, because they are now wrapped  in in a `LazyProperty`. The `LazyProperty` needs to be evaluated because some checks are done on the type of `$value`, i.e `is_array` etc... in `validateGenericNode`.I'm concerned that the original PR didn't really add sufficient test coverage for the introduction of `LazyProperty`, and I'm not 100% sure that I've caught all the cases where the `instanceof` check are needed in this PR.For the tests, I added the `@dataProvider getConstraintMethods` to every test that hit the problem area of code.~~The only issue is that my fixed has broken the test introduced in#36343, `testGroupedMethodConstraintValidateInSequence`.~~~~I think I need@HeahDude to help me work through this. Maybe there is a more simple solution, one that doesn't require doing `instanceof LazyPropery` checks in multiple places, because this feels very brittle.~~EDIT: fixed that test.Commits-------281861e [Validator] fix lazy property usage.