[1.x] Use named routes on Inertia with Ziggy

[m1guelpf]

Description

This PR replaces all URLs on the Inertia skeleton with named routes, making use of the Ziggy package from Tighten.

Related Issues

Closes #157

Future Improvements

I wasn't able to replace the URLs on the two-factor authentication component since their routes aren't named. If requested, I could submit a PR to fortify that adds names for these routes for completion's sake.

[driesvints]

Think we'll need to target 2.x here since ziggy is now basically required and existing installs won't have the dependency.

[taylorotwell]

@m1guelpf I don't think it matters since this only really affects the installation process and stubs. Existing apps won't have it but new apps will.

[driesvints]

@taylorotwell correct, didn't saw that only the stubs were updated 👍

[taylorotwell]

@m1guelpf after merging this and testing locally I get 419 CSRF problems on every POST.

Yeah, confirmed twice. I use most recently tagged laravel//jetstream + Inertia and everything is fine. I use Jetstream edge after this PR is merged and I get CSRF problems on POST (for example password confirmation or even logout).

[m1guelpf]

I don't get how this should affect anything, the result should be exactly the same

[taylorotwell]

@m1guelpf you don't have this problem?

[m1guelpf]

I didn't, but I also didn't fully test all endpoints (just made sure no pages throwed errors and tried a few), so it's possible I didn't trigger any POST ones. The interesting thing is, if you dd on the tokensMatch function of the VerifyCsrfToken middleware before the check, both tokens match, but if you let the check happen, they fail.

[taylorotwell]

So you are able to reproduce what I'm talking about now?

[m1guelpf]

Found the issue, submitting another PR