Expose `ReflectionUtils.isAssignableTo` via `ReflectionSupport`

[scordio]

I'm implementing a @MethodConversion argument converter that delegates the value conversion to a static method via reflection, inspired by #4993 (reply in thread).

To identify the appropriate method for all use cases I want to test, I ended up reimplementing ReflectionUtils.isAssignableTo(Class, Class) (I cannot use it directly, although unsupported, due to the module system).

Would you consider exposing isAssignableTo via ReflectionSupport?

My implementation currently needs isAssignableTo(Class, Class) only, but maybe it makes sense to expose the other overload, too.

I'd love to have it on version 5, if possible 🙂

Deliverables

• Expose isAssignableTo via ReflectionSupport

[scordio]

Related to this, I realized I'll eventually ask for parseFullyQualifiedMethodName and parseFullyQualifiedFieldName as well (the latter for a @FieldConversion converter that I haven't started yet).

Let me know in case it's best to raise a separate issue for them!

[sbrannen]

I realized I'll eventually ask for parseFullyQualifiedMethodName and parseFullyQualifiedFieldName as well

The former has already been requested in #2995.

Let me know in case it's best to raise a separate issue for them!

So, I suppose it would be better to request parseFullyQualifiedFieldName() in #2995 as well.

Actually, it might be best to request isAssignableTo() there as well and just have one issue for all of them.