Added possibility to extend ModelAttributeMethodArgumentResolver , in order to populate objects in same way, but with different set of data.

Example use-cases: - I want to populate object with data from headers, instead of common set of fields for model attribute resolution; - I want to manipulate with field values before set them to POJO in controller in case of custom annotated object

This is pretty much available in non-flux ModelAttributeMethodProcessor (since we can extend that and override some methods)

Logic in this class pretty much complicated to copy-paste or write own resolver, so I guess it's better to allow reuse code with possibility to add own data to bind.