fix: Prevent view caching for blade directive

[saibotk]

This reintroduces similar behavior as Ziggy implements.
When generating the Blade output the code was automatically cached by
Laravels view system and thus always needed an php artisan view:clear when
introducing new routes and using the blade directive.

This now acts the same as Ziggy does. Please note, that Ziggy once
did also cache the view but returned to this approach, as it breaks
in certain scenarios and has no impactful performance impact:
See tighten/ziggy#349

[pedroborges]

We are also running into this issue. I would love to see this PR merged 🤞

[mxmtsk]

Want to push for this to be merged as well, since this package as it is currently doesn't work in a multi-tenant, multi-domain application, since the url property is cached too, leading to CORS errors and requesting to wrong domains altogether.

For everyone having the same issue, to overcome this, before it is merged, I just created a custom directive in AppServiceProvider based on your fix:

    /**
     * Register any application services.
     */
    public function register(): void
    {
        Blade::directive('uncachedtrail', fn () => "<?php echo app('" . TrailBladeGenerator::class . "')::generate(); ?>");
    }

Thank you for this!

[saibotk]

You can at this point also go back to ziggy which also has types being generated now