Automatically fix blade variable typos and optional variables

[MrRio]

This PR adds a solution for fixing undefined variables in view files.

The Solution Provider

• It starts by looking at how similar the variable name is to viewData that's already passed in. If it's above a threshold it shows these solutions first, in order of most similar.
• After that, it offers to make the variable optional in the blade template by adding ?? ''

The Solutions

• Both solutions start by loading the blade template, and making an in-memory change
• The original and resulting blade templates are then compiled to PHP using the Blade Compiler
• The PHP is then tokenized
• We modify the tokenized original to our expected output
• The actual tokenized output is compared to the proposed resulting file, if they don't match, the solution action is never offered to the user, but the suggestion text is.

This is to ensure we never break a blade template, it also allows us to build upon the basic find and replace logic in the future.

Automated Tests

There are some automated tests around this, we can expand to include more difficult cases.

[freekmurze]

This looks awesome. I’ll review it soon. Thanks!

[MrRio]

Thanks! :)

[MrRio]

I'm happy with this if you are, will use draft PRs in future while I'm still working on it

[MrRio]

Thanks for the feedback. All sorted!

[MrRio]

Good to merge?

[freekmurze]

Some more nitpicks. After that I think it'll be ready for merge.

Awesome PR 👍

[MrRio]

This is good to merge. 👍

[mpociot]

Great job on this PR! Thank you!