Update view "version" variable name to avoid potential conflicts

[pb30]

Summary

We inherited a number of projects that have a global version variable shared with all views that is an array of things like asset versions, etc.

When running php artisan ide-helper:generate it results in an error since $version is used in this packages views.

Array to string conversion at vendor/barryvdh/laravel-ide-helper/resources/views/helper.php:17

This PR renames the variable to $laravel_version to avoid conflicts since it may be a common global variable name.

Type of change

• Misc. change (internal, infrastructure, maintenance, etc.)

Checklist

• Existing tests have been adapted and/or new tests have been added
• Add a CHANGELOG.md entry
• Update the README.md
• Code style has been fixed via composer fix-style

[mfn]

LGTM!

I don't understand how the conflict happens, but I don't mind the change.

If there can be pollution/conflict, it would probably be best to prefix all the vars with $ide_helper_* or so.

[barryvdh]

Hmm I think it's a bit odd that we need to account for all possible variables. If someone (slight chance) has overriden the template, this would be considered BC break.