Add a customizable authentication action

[convenimus]

just a quick heads-up: English is not my first language, so I used AI to help translate and write this message more clearly.

I would like to suggest adding a way to customize what happens during authentication after a passkey has been verified.

Right now, the package allows overriding actions like storing passkeys through the config file. But the actual login process is fixed. In many cases, developers need more control at this point. For example, to check user permissions, log custom events, or return a custom response like an Inertia page instead of a redirect.

To make this possible, I propose adding a new action that handles the authentication step. This would let developers replace it with their own logic using Laravel’s service container, just like the other actions already supported.

This small change would make the package much more flexible without breaking existing functionality. It would also fit well into the current structure of the package.

I’d be happy to help with the implementation or a pull request if you think this makes sense.

[freekmurze]

Feel free to submit a PR.