Add support for tuple route generation

[spaceemotion]

I was unsure which approach to take, but I ended up with reading out the actual value from the UrlGenerator class itself, rather than trying to analyze the RouteServiceProvider. Seemed like the most stable solution to me.

Fixes #321

[jasonmccreary]

Per the issue comments, let's make this configurable, not simply based off the RouteServiceProvider.

[spaceemotion]

@jasonmccreary changed it to use config() instead 👍

[jasonmccreary]

Much cleaner. 👍

I'll get this merged once the tests pass and I make some tiny text tweaks. However, I may wait to tag until next week. You can use dev-master if you want it right away.

[jasonmccreary]

Unfortunately, this is not (currently) allowed unless the RouteServiceProvider::$namespace property is empty.

[spaceemotion]

There could be a note about this in the config file.

[jasonmccreary]

Unfortunately the FQCN is only allowed with the tuple syntax. In order to use an FQCN for a single route (or resource) you must unset the namespace property within your RouteServiceProvider.

So, while I still like the config, in order to fully achieve what you're after, there would also have to be some additional logic to check that property again. Which I'm on the fence about...

[spaceemotion]

Since this is a configurable value, my guess is that this should be a deliberate action by the user. If they enable it without knowing what it does...

[jasonmccreary]

Hmmm... I considered a PR to the framework to allow the FQCN even with this RouteServiceProvider property set. But according to Taylor, it seems as though this property is no longer set by default starting with Laravel 8.

As such, I am comfortable with it as is, and to your point, guiding users to unset the property and/or upgrade to the latest version.

However, we may wish to change the option name to generate_fqcn_routes or something...

[spaceemotion]

Hm, if Laravel 8 will leave the value blank, the config value shouldn't just be false by default then, right? Probably should check Application::VERSION if it starts with 7 and disable it.