Remove route model binding for users

[duncanmcclean]

This pull request resolves #2316, where issues crop up in existing Laravel apps if people are using route model binding to bind to their User model.

This PR just straight out removes the route model binding and replaces it with a lookup in the controllers where it is referenced with Entry::find($id).

While working on this PR, I've also found posts on the Discord by some developers complaining that Statamic's route model binding is a bit generic and can cause issues if used side by side on an existing Laravel app. I'm happy to make any changes to any of the other route model binding stuff if that's something you'd like me to do.

Let me know if you have anything you'd like me to change.

[duncanmcclean]

Instead of removing route model binding entirely, maybe we could just rename the route model binds to being Statamic specific, like statamic_user, etc which would resolve any Statamic binding issues. Feel free to decline this PR if you'd like me to do that instead.

(thanks @edalzell for that idea)

[riasvdv]

To be functionally the same as route model binding you need to do User::findOrFail($id)

[duncanmcclean]

To be functionally the same as route model binding you need to do User::findOrFail($id)

Ah, good point! The only issue is... there's no findOrFail method on the UserRepository, see here.

[edalzell]

Also see here: #3055

[jasonvarga]

404s need to be thrown when the user in the url doesn't exist. You can copy the logic that you removed from the service provider.

[duncanmcclean]

404s need to be thrown when the user in the url doesn't exist. You can copy the logic that you removed from the service provider.

Added the throw_unless to the controllers.

[jasonvarga]

Either remove the messages from the exceptions, or make sure you're passing the handle in from the route argument.

Right now since you're using $user = User::find($user) before new-ing up the exception, the message will be User [] not found. but it should be User [whatever] not found.

Since you don't ever see the exception messages, it's probably fine to just remove them.

[duncanmcclean]

Either remove the messages from the exceptions, or make sure you're passing the handle in from the route argument.

Right now since you're using $user = User::find($user) before new-ing up the exception, the message will be User [] not found. but it should be User [whatever] not found.

Since you don't ever see the exception messages, it's probably fine to just remove them.

I've removed the exception messages.