Fix: used new parent relation on instanceof control for has one through

[musaberatbahadir]

Description

fix for the issue I created. CreateAction is checking the correct class on instance of control now.

[danharrin]

This would break Laravel 10.x compatibility, right? Can you do a class_exists() check and check the correct parent class based on that please?

[musaberatbahadir]

@danharrin I've added the check you have mentioned above

[musaberatbahadir]

@danharrin I also realized that instanceof HasManyThrough control causes other errors on my project like in Filament\Tables\Table\Concerns\HasQuery, do you want me to replace all of them as I did on the last commit, or do you wanna introduce some config level check by controlling laravel version or class_exists function?
there are 6 more instanceof HasManyThrough control

[danharrin]

Please can you do the class_exists() in all places?

[musaberatbahadir]

Done! @danharrin

[danharrin]

Does the return type of getRelationship() need updating? Any other references to this class?

[danharrin]

If we did, I think we would need to retain both HasManyThrough and HasOneOrManyThrough on the return type for backwards compatibility, right?

[musaberatbahadir]

Good catch! I fixed that too.

[danharrin]

Thanks