Fix path resolution during optimize with Sentry

[ganyicz]

The scenario

Running php artisan optimize with Sentry installed produces broken compiled templates — components aren't compiled to functions.

Running php artisan view:cache alone works fine.

The problem

app('blade.compiler')->getPath() always returns null during optimize, so we skip the wrap() call entirely. This happens because the instance resolved via app('blade.compiler') is different from the one that started view compilation.

Sentry forces early resolution of the blade engine during boot via app('view')->getEngineResolver()->resolve('blade'). When php artisan optimize runs:

1. config:cache — swaps the application instance in the container.
2. view:cache — compiles views using the original app instance from $this->laravel.

Because of the early resolution, Laravel doesn't resolve the blade compiler again from the new instance and instead uses the stale one. Calling app('blade.compiler') returns a new instance that has no path set.

The solution

We capture the compiler reference once in BladeService::earliestPreCompilationHook() and thread $path through the entire blaze pipeline, instead of resolving app('blade.compiler') inside each BlazeManager method:

$compiler = app('blade.compiler');

$compiler->prepareStringsForCompilationUsing(function ($input) use ($callback, $compiler) {
    $path = $compiler->getPath();

    return $callback($input, $path);
});

Fixes #43