Idea: Rework session service implementation to use the new axum 0.6 state pattern

[maxcountryman]

As mentioned here and explained in more detail here.

[Ptrskay3]

Correct me if I'm wrong, but State is for global application resources, which is the same for all requests, such as database pools or email clients. On the other hand though, the session we add as an extension to the request is local, and differ from request to request.

[maxcountryman]

Yes, I think you are right. (It's a bit confusing how the new middleware docs mention state now.)

That said, while this has no practical bearing on things (it does not provide additional type safety, for example), I did reorganize the axum-login middleware a bit.

We could potentially do something similar here but again I don't think it makes much of a difference in practice.

[maxcountryman]

Closing this for now.