Having a getType() method on an extractor is not enough. Such a method may
exist to be forward-compatible with the TypeInfo component. We still must
not call it if the TypeInfo component is not installed to prevent running into
errors for not-defined classes when the TypeInfo component is not installed.

…ng TypeInfo classes (xabbuh)

This PR was merged into the 7.1 branch.

Discussion
----------

[Serializer][Validator] prevent failures around not existing TypeInfo classes

| Q             | A
| ------------- | ---
| Branch?       | 7.1
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        |
| License       | MIT

Having a `getType()` method on an extractor is not enough. Such a method may exist to be forward-compatible with the TypeInfo component. We still must not call it if the TypeInfo component is not installed to prevent running into errors for not-defined classes when the TypeInfo component is not installed.

Commits
-------

386453ee77b prevent failures around not existing TypeInfo classes

* 7.1:
  Removed body size limit
  prevent failures around not existing TypeInfo classes
  fix version check to include dev versions

…ility

Signed-off-by: wanxiangchwng <[email protected]>