Fix: Prevent laravel/sanctum from going beyond version 4.2.4

[ollieread]

If anyone runs any form of composer update they'll get laravel/sanctum version 4.3.1, but 4.3.0 introduced a breaking change that will cause errors in Pterodactyl installs.

In \Pterodactyl\Extensions\Laravel\Sanctum\NewAccessToken you're relying on the underlying class' (\Laravel\Sanctum\NewAccessToken) lack of typing on the accessToken property. In Laravel Sanctum 4.3.0 the laravel/sanctum#586 PR changes were released, which refactors the underlying class to use property promotion, and specifies a type.

https://github.com/laravel/sanctum/blob/224864063d51d6adddc8c061ccf61eafa0e8f7ce/src/NewAccessToken.php#L10-L18

[WeeskyBDW]

Woudn't be "easier" to fix the issue ? Or you prefer not ?

[ollieread]

Woudn't be "easier" to fix the issue ? Or you prefer not ?

@WeeskyBDW the issue is that Pterodactyl has a bit of a hack around this part and fixing the cause of it would require most likely a chunk of work. Locking the version like this is the quickest way to not break everyone's api keys if they get a later version of sanctum.