Errors not getting grouped when they are the same from inside blade files

### Environment

How do you use Sentry?
Sentry SaaS ([sentry.io]())

Which SDK and version?
sentry.php.laravel 2.8.0

### Steps to Reproduce

Whenever an error happens from inside a blade file, they are added as a new issue, if the error was in a different version. (we clear blade cache on each release)


When looking at the stacktrace, the reason it doesn't group them might be because of `param0`, which contains the hashed id of the cached blade file. This means when we clear the cache, that id will be different, and sentry will detect it as a different issue.


Another plausible reason could be that sentry reports that the stacktrace cannot be found for issues, as long as the issue happens inside a blade file. (warning is not shown in non blade files)


Start by reproducing the Blade-file error across releases while clearing the Blade cache, then compare the reported stack traces and grouping data, especially param0. Confirm whether the cached Blade file identifier or missing stack trace prevents grouping; done means equivalent errors group together across cache-clearing releases.

Written by the indexing model from the issue text.