fix(laravel): disable plugins on non-laravel projects

[angelogambaradev]

📑 Description

The PR disables Laravel plugins that interfere with other imports.

📖 Additional Information

Unless a file named artisan is found on the root of the project, all additional Laravel plugins are disabled.

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• Proper usage of opts table rather than setting things up with the config function.

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

[ALameLlama]

the lint in complaining about this but this would be good to have

[angelogambaradev]

the lint in complaining about this but this would be good to have

Sorry for not replying. I misunderstood you for some AI bot. Also, the grammar...

[Uzaaft]

the lint in complaining about this but this would be good to have

Sorry for not replying. I misunderstood you for some AI bot. Also, the grammar...

Rude.

Stale review already adressed.