Allow custom mutex names for isolated commands

[rybakihor]

Title: Allowing custom mutex names for isolated commands

Description:
This pull request introduces a modification to the commandMutexName function in order to support custom mutex names for isolated commands in Laravel's framework. Previously, all commands with the same name were being blocked simultaneously, regardless of their parameters. With this update, isolated commands can define their own identifier using the getIsolatedMutexName method.

Changes Made:

• Updated the commandMutexName function in the framework directory to include the command's isolated mutex name, if provided.

• Added a conditional check using method_exists to determine if the getIsolatedMutexName method is available for the command.

• If the getIsolatedMutexName method exists, the isolated mutex name is appended to the base name of the command's mutex.

• If the getIsolatedMutexName method is not present, the base name of the command's mutex is returned as before.

This modification enables more granular control over command execution, allowing isolated commands to have unique mutex names even if they share the same command name. This is especially useful when we want to block the simultaneous execution of a command with the same parameters, but not to block the execution of this command with other parameters.