[5.7] Remove Hash::check() for password verification

[crynobone]

As of 5.7.0, Laravel now verify the hash algorithm before using password_verify(), while this is more secure for hashing in general this cause a regression bugs for password verification on authentication flow:

• Laravel now only allow application using bcrypt to verify bcrypt password, any older hashing is no longer supported. [5.7] Hash::check breaks all apps with legacy hash #25586
• You no longer able to change from bcrypt to a stronger algorithm on your existing applications. [5.7] Mixing hashing algorithms not working #25458

[gabrielpeixoto]

I believe the problem continues in the laravel passport. When requesting token using password grant

[mnabialek]

@crynobone @taylorotwell This is breaking change. Today I've updated my app from 5.7.2 to 5.7.4 and suddenly my authentication stopped working. The thing is that someone might have custom hasher created (as I have, not using bcrypt) and this hasher should be used to verify if password is correct.

[taylorotwell]

We need to revert this.

[crynobone]

I don't agree with the framework checking on algo for password verification process, this PR was build to work around the BC made on 5.7.0.

Personally I would prefer the algo check verification be made as a new method if one where really wanting strict algo verification such as Hash::verify().