Fix #1300 relation_return_type must take precedence if it is defined

[menthol]

Summary

The rrelation_return_type must take priority if it is defined so that the choice that the user imposes in the options is used without the automatic detection overloading it.

Currently, it is not possible to define a one relationship if somewhere in the name of the relationship object there is the word Many.

ex:

# Model
public function propertyManagementCompany(): Staudenmeir\EloquentHasManyDeep\HasOneDeep
    {
        return $this->hasOneDeep(PropertyManagementCompany::class, ['landlord_user', User::class, 'property_management_company_user']);
    }

# config/ide-helper.php
    'additional_relation_types' => [
        'hasOneDeep' => \Staudenmeir\EloquentHasManyDeep\HasOneDeep::class,
    ],
    'additional_relation_return_types' => [
        'hasOneDeep' => 'one', # No many, no morphTo, no falsy
    ],

# currently generate
/**
 * @property-read \Illuminate\Database\Eloquent\Collection|\App\Models\PropertyManagementCompany[] $propertyManagementCompany
 * @property-read int|null $property_management_company_count
 */

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Misc. change (internal, infrastructure, maintenance, etc.)

Checklist

• Existing tests have been adapted and/or new tests have been added
• Add a CHANGELOG.md entry
• Update the README.md
• Code style has been fixed via composer fix-style

[barryvdh]

Closing to trigger tests

[barryvdh]

Thanks