[Feature Request]: Prefer to use published stubs when generating code

[raveren]

Feature Description

First of all, it's a pleasure to use your plugin, it's a masterpiece, thank you thank you thank you!!!!

Now the issue:

I was wondering why the Laravel Idea code generation was not using the stubs that were explicitly customized (you do it by first publishing all and then leaving the one(s) you want in the /stubs dir).

It turns out the plugin is using the code templates hidden deep within PHPStorm settings: https://github.com/laravel-idea/plugin/issues/49 :)

I think it makes sense to first check if appropriate stub exists and only if not - use the non-shareable, difficult-to-discover code template setting.

My usecase: a legacy codebase our team is working on is using different name for created_at columns so I extended the Blueprint->timestamps() method to use the consistent names when creating new migrations. It's an abbreviated example, there's more, but that's the gist.

[emotality]

+1 ! Can the code generation please use our stubs instead of plugin stubs 😢

I've been using this plugin for like 3 years only for the fast autocomplete 😅 only saw now that we can use these code generations 🤣 but ALLL my stubs are custom and reuse it in every project, code generation makes it feel redundant if it just generates empty classes instead of our custom stubs that are filled with goodies 🥹🥹🥹

Thanks for helping me code faster for the past 3 years though ☺️❤️