Use static properties for Team and Membership too

[mallardduck]

Keeping some parody with the way the User model is managed by the Jetstream service, the Team and Membership models are now treated the same way.

This was inspired by #118 since that made me realize editing models location wouldn't be done in a consistent manner. So if all you wanted to do was point models to a different location you'd be overriding properties and methods. So by exposing all as static properties, now you only would add properties to your extension of Jetstream.

---

What extending Jetstream to adjust models looks like:

Before:

<?php


namespace App;

use App\SomeOther\Folder\User;

class MyJetstream extends \Laravel\Jetstream\Jetstream
{
    public static $userModel = User::class;

    /**
     * Get the name of the team model used by the application.
     *
     * @return string
     */
    public static function teamModel()
    {
        return 'App\\SomeOther\\Folder\\Team';
    }

    /**
     * Get the name of the team model used by the application.
     *
     * @return string
     */
    public static function membershipModel()
    {
        return 'App\\SomeOther\\Folder\\Membership';
    }
}

After

<?php


namespace App;

use App\SomeOther\Folder\User;
use App\SomeOther\Folder\Team;
use App\SomeOther\Folder\Membership;

class MyJetstream extends \Laravel\Jetstream\Jetstream
{
    public static $userModel = User::class;
    public static $teamModel = Team::class;
    public static $membershipModel = Membership::class;
}

[taylorotwell]

Thanks but we should also add methods to set these without having to extend the class.

[mallardduck]

@taylorotwell - good call, I overlooked that existing already for User.
Will send over an additional PR soon.

[mallardduck]

@taylorotwell if I were to document the use*Model methods somewhere in the docs repo, where do you think makes more sense?

1. Getting Started > Configuration
2. Customization > Models