Don't throw if macro is not recognizable

[hackel]

Currently, if a macro is registered improperly or in a format that this package doesn't recognize, it throws an exception. e.g.

ReflectionException: Method Illuminate\Support\Carbon::__invoke() does not exist

This simply ignores the error and continues.

[KristofMorva]

@hackel are you sure it's a great idea to ignore such mistakes? Like, if I made a typo in the macro name, it'll just be ignored, I'll see that the macro helpers are not generated, but will have no idea why.

What's the use case for such change?