[12.x] Adds resolver for specific Model route binding fields

[DarkGhostHunter]

What?

This PR allows the developer to transform incoming route binding fields values, instead of overriding the Route Binding methods. The main problematic that it solves modifying the field value or query.

The developer can use resolveField() on the target model to register a callback that will be executed for the specific implicit binding field. The callback receives the value, field name, and query builder. The developer may return a new field value, or completely hijack the query for better control.

In the following example, the Car model doesn't have an ulid column. Instead of creating that column in the database, we can resolve the ulid field and transform the query to find the record by its UUID:

use Illuminate\Database\Eloquent\Model;
use Symfony\Component\Uid\Ulid;

class Car extends Model 
{
    public static function booted()
    {
        static::resolveField('ulid', function ($value, $field, $query) {
            return $query->where('id', Ulid::fromString($value)->toRfc4122())
        })
    }
}

When the callback doesn't return an Eloquent Query or Base Query, it will use the returned value as part of the where key:

Car::resolveField('id', function ($value) {
    return Str::of($value)->snake()->lower()->toString();
});

Also, because the field resolver is a callable, the user can register invokable class instances as resolver if needed, especially if their logic is too much for a single function.

Car::resolveField('uuid', new UuidResolver())

Finally, the resolver can be deleted by setting null.

Car::resolveField('uuid', null);