Use route keys for email verification

[LaravelFreelancerNL]

Both Laravel & Fortify use the primary key of a user model for email validation URL's.

However I have a use case where the primary key breaks the URL structure as it contains a slash. In this case the _id of an ArangoDB document. Although I could set the primary to the _key value which is more SQL style id-like this causes other problems particularly with (graph) relationships.

So the neatest way I can think of is using the designated route key for the URL generation and check.
Am I missing something?

I'm assuming this may cause backwards-compatibility problems for some users. So if you folks see this as an improvement for the framework/fortify I'll make some pull requests to the master branches.