* Deprecate `TestUtils.getPropertyValue()` based on a `Class` param
* Optimize `TestUtils.getPropertyValue()` to not create extra `DirectFieldAccessor`
if we are at the end of the nested path
* Refactor project code to use a new `TestUtils.propertyValue()`
* Remove unnecessary now `@SuppressWarnings("unchecked")` from those tests
* Some other code clean up in affected test classes

…rtyValue()`

Turned out we don't need a new method with generics.
And we don't need an extra argument to resolve the type.
There is just enough to have a simple cast to generic argument.
In the end we are talking only about tests.

* Remove redundant (just created `TestUtils.propertyValue()`)
* Change `TestUtils.getPropertyValue()` signature for generic argument
* Refactor affected tests

With a new style we don't have a paradox of choice for this or that method.
The generic argument on the method is enough to cover all use-cases,
even if we have to add `<Object>` to satisfy `assertThat()` expectations.
We don't need an extra `Class` argument to verify value compatibility.
The simple cast to generic type is enough got tests environment.
This is slightly breaking change in the API, but that is only for tests anyway