Move registering routes to boot method of ServiceProvider

[jnoordsij]

According to Laravel docs, registering routes should never happen within the register method, as only binding should happen there. In practice, this causes a problem when trying to override/extend the base Laravel FilesystemServiceProvider, which combined with registering this package triggers an Illuminate\Contracts\Container\BindingResolutionException with message Target class [files] does not exist..

Therefore, moving the registering of routes to the boot method looks like a more robust approach to me. See also the example from the Laravel docs on the loadRoutesFrom method.

[PrinsFrank]

This issue is also solved in #1252 by marking the serviceProvider deferrable.

[jnoordsij]

@barryvdh any chance you have some time to check this? It should be a quick and clear fix I think.

[jnoordsij]

Actually, I see #1197 already proposed this earlier. Closing this in favor of that, hoping it can be merged soon!