Update Laravel alias to use the correct path for Composer global binaries.

[adbarbosa]

Description

This pull request updates the laravel alias in Bash-it to reference the correct path for globally installed Composer binaries (~/.config/composer/vendor/bin/laravel). This change ensures that users can execute the laravel new command without needing manual adjustments to their environment's PATH.

Motivation and Context

The default path for Composer global installations has changed from ~/.composer to ~/.config/composer. Without this update, users with the default Composer configuration encounter issues when trying to use the laravel alias, as it points to the outdated path.

This change resolves the issue and aligns Bash-it's Laravel alias with Composer's current global installation directory structure.

No open issues were directly linked to this problem at the time of submission.

How Has This Been Tested?

• Tested locally on a Linux environment with Composer and Laravel installed globally.
• Verified the updated alias correctly points to ~/.config/composer/vendor/bin/laravel.
• Confirmed the laravel new command successfully creates a new Laravel application using the alias.
• Ensured no adverse effects on other Bash-it functionality.

Screenshots (if appropriate):

N/A

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• If my change requires a change to the documentation, I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
• I have added tests to cover my changes, and all the new and existing tests pass.

[seefood]

See remark and fix if relevant, or mark it resolved if you are 100% sure it's not. Thanks!

[seefood]

Any chance some users still use the old location on older installations and will somehow lose functionality? I have a feeling this can benefit from an "if" and a fallback location if an older installation is found.

[seefood]

@adbarbosa