[11.x] Introduce HasUniqueStringIds

[cosmastech]

At work, we have a custom unique identifier type that we are using in place of UUIDs. (They are kind of like Amazon's ARNs).

I wanted to be able to use these as route keys, which works fine if I do something like this:

trait HasTwrnsTrait
{
    use HasUuids;

    public function newUniqueId(): string
    {
        return (string) Twrn::new();
    }

    public function resolveRouteBindingQuery($query, $value, $field = null)
    {
        if ($field && in_array($field, $this->uniqueIds()) && ! Twrn::isValid($value)) {
            throw (new ModelNotFoundException)->setModel(get_class($this), $value);
        }

        if (! $field && in_array($this->getRouteKeyName(), $this->uniqueIds()) && ! Twrn::isValid($value)) {
            throw (new ModelNotFoundException)->setModel(get_class($this), $value);
        }

        return parent::resolveRouteBindingQuery($query, $value, $field);
    }
}

This seemed a little bit cumbersome to have to duplicate the resolveRouteBindingQuery() logic only to change Str::isUuid(). Additionally, it's a maintenance burden.

The goal with this change is to make a more generalized trait which can be extended to make building custom string unique keys/routing by those custom implementations. As a bonus, this also consolidates the code between HasUlids and HasUuids.

With this change I can create a quick trait like this.

trait HasTwrnsTrait
{
    use HasUniqueStringIds;

    public function newUniqueId()
    {
        return (string) Twrn::new();
    }
  
    protected function isValidKey($value): bool
    {
        return Twrn::isValid($value);
    }
}