[9.x] Improve UUID and ULID support for Eloquent

[driesvints]

Improves upon #44074 by:

• Allowing to more easily use the trait to just be used on non-primary key columns
• Adds a special ulid column on Blueprint that creates a char(26) behind the scenes
• Automatically sets incrementing to false when a string type primary key is used
• Adds more tests

I was doubting on checking to see if I could add support to use both traits at the same time (so you could both fill in UUID and ULID columns) but I guess that scenario isn't so common.

[driesvints]

This might need to be rethought. In my mind a string key type column can never be incrementing but I might be wrong.

[driesvints]

I had to rewrite the test here because of the change I did in the getIncrementing method. I think the current test wasn't realistic as I can't see how you can increment with string-based keys. With string-based keys you always need to set them beforehand afaik (like I adjusted the test to).

[taylorotwell]

@driesvints why was the change to getKeyType not needed on HasUlids too?

[driesvints]

@taylorotwell whoops, you're right. Pushed.

I first was thinking of doing it through a property but when you apply a trait with a property directly on a model you cannot overwrite it. The current solution is way better and more frictionless :)

[martio]

Good job! 👍

[martio]

Maybe it's nice to add support for a binary column type for UUID? 😏

[The-Hasanov]

Hi @driesvints . This update break jenssegers/laravel-mongodb
mongodb/laravel-mongodb#2451

public function getIncrementing()
{
    if ($this->getKeyType() === 'string') {
         return false;
       }

      return $this->incrementing;
 }

[driesvints]

@The-Hasanov I replied on the related PR fix: mongodb/laravel-mongodb#2452