#372 - spatie permissions update

[kamilpiech97]

Should close #372.
Updated migrations for properly running tests - in migrations updates are connected with getting variables when tables are creating.
Example, before:

[$columnNames["team_foreign_key"], PermissionRegistrar::$pivotPermission, $columnNames["model_morph_key"], "model_type"],

after:

[$columnNames["team_foreign_key"], $pivotPermission, $columnNames["model_morph_key"], "model_type"],

and $pivotPermission is retrieved on the top of migration file, like that:
$pivotPermission = $columnNames["permission_pivot_key"] ?? "permission_id";

Also, we can stay with normal ids in permissions, we do not need to change them into uuid.

[krzysztofrewak]

Okaaay, but what about production environment? We won't run these migrations there.

[EwelinaSkrzypacz]

Okaaay, but what about production environment? We won't run these migrations there.

On beta environment it seems like it works without running migrations 👀

[kamilpiech97]

Okaaay, but what about production environment? We won't run these migrations there.

On beta environment it seems like it works without running migrations 👀

We do not need to run updated migrations because they do not change the database, only the logic of creating tables, and we update them only for tests.

[kamilpiech97]

We do not need to run updated migrations because they do not change the database, only the logic of creating tables, and we update them only for tests.

We do not need to run updated migrations because they do not change the database, only the logic of creating tables, and we update them only for tests.