[v7] Update Role contract to match implementation and fix PhpStan errors

[SanderMuller]

Allow BackedEnum and set default guardName

Fixes the following PhpStan error:

 ------ -------------------------------------------------------------------- 
  Line   app/Console/Commands/EnsureRolesAndPermissionsAreSetCommand.php     
 ------ -------------------------------------------------------------------- 
  29     Method Spatie\Permission\Contracts\Role::hasPermissionTo() invoked  
         with 1 parameter, 2 required.                                       
         ✏️  app/Console/Commands/EnsureRolesAndPermissionsAreSetCommand.php  
  29     Parameter #1 $permission of method                                  
         Spatie\Permission\Contracts\Role::hasPermissionTo() expects         
         Spatie\Permission\Contracts\Permission|string,                      
         App\Enums\Permissions\PermissionEnum::LOGIN_AS_ANY given.           
         ✏️  app/Console/Commands/EnsureRolesAndPermissionsAreSetCommand.php  
 ------ -------------------------------------------------------------------- 

caused by this line in my application:
$role->hasPermissionTo(PermissionEnum::LOGIN_AS_ANY)

I am passing an enum instance which is allowed according to the docs, and works, but the interface Docblock does not support this. The other error says I am required to pass two parameters, while the second param ($guardName) is optional according to the implementations, but not according to the interface

[drbyte]

I agree with your point.
It may be a breaking change for many though.
So may have to hold off on this for awhile.

[SanderMuller]

I agree with your point. It may be a breaking change for many though. So may have to hold off on this for awhile.

Maybe we can just update the dockblocks as a patch and then the actual types in a major version?

[drbyte]

Yes, that'd be fine.

[drbyte]

Added BackedEnum in 59b966f

[spatie-bot]

Dear contributor,

because this pull request seems to be inactive for quite some time now, I've automatically closed it. If you feel this pull request deserves some attention from my human colleagues feel free to reopen it.