Route macro functions: add backed enum support

[Yi-pixel]

It might be simpler to use the following approaches, but they will break the previous tests (because the middleware name returned is the full class name, not the alias)

\Spatie\Permission\Middleware\PermissionMiddleware::using();
\Spatie\Permission\Middleware\RoleMiddleware::using()

[drbyte]

I like this.

And your comment about using FQDN::using() is good too. Perhaps we can incorporate both? (Add them, vs changing prior ones)

[Yi-pixel]

I like this.

And your comment about using FQDN::using() is good too. Perhaps we can incorporate both? (Add them, vs changing prior ones)

@drbyte Hmm, but with the current approach, allowing a mix of Backed Enum and strings looks pretty good.

Route::permission(['view-post:1', Permission::ReviewPost])

---

However, if switching to FQDN::using(), there are some issues to be aware of.

As mentioned earlier, FQDN::using() generates the fully qualified class name, whereas the current implementation uses middleware aliases. This means that if the alias in the actual code points to a custom middleware, it could break things (though the likelihood is low).

Alternatively, it might be worth considering modifying FQDN::using() to use middleware aliases instead, ensuring consistent behavior.

[drbyte]

Will merge this for now. The other adjustments for using() can be explored separately.