fix(docs): ensure class member order follows source

- Fixes issue where class members are sometimes listed alphabetically instead of by source in middleware documentation.(#4393)
- Updates references to use the base module.

Author: Umpire2018

docs/reference/middleware/index.rst

@@ -1,9 +1,9 @@
 middleware
 ==========
 
-.. automodule:: litestar.middleware
-
-
+.. automodule:: litestar.middleware.base
+    :members:
+    
 .. toctree::
     :maxdepth: 1
 

docs/release-notes/whats-new-2.rst

@@ -187,11 +187,11 @@ Imports
 +----------------------------------------------------+------------------------------------------------------------------------+
 | ``starlite.AuthenticationResult``                  | :class:`.middleware.authentication.AuthenticationResult`               |
 +----------------------------------------------------+------------------------------------------------------------------------+
-| ``starlite.AbstractMiddleware``                    | :class:`.middleware.AbstractMiddleware`                                |
+| ``starlite.AbstractMiddleware``                    | :class:`.middleware.base.AbstractMiddleware`                           |
 +----------------------------------------------------+------------------------------------------------------------------------+
-| ``starlite.DefineMiddleware``                      | :class:`.middleware.DefineMiddleware`                                  |
+| ``starlite.DefineMiddleware``                      | :class:`.middleware.base.DefineMiddleware`                             |
 +----------------------------------------------------+------------------------------------------------------------------------+
-| ``starlite.MiddlewareProtocol``                    | :class:`.middleware.MiddlewareProtocol`                                |
+| ``starlite.MiddlewareProtocol``                    | :class:`.middleware.base.MiddlewareProtocol`                           |
 +----------------------------------------------------+------------------------------------------------------------------------+
 | **Security**                                                                                                                |
 +----------------------------------------------------+------------------------------------------------------------------------+

docs/release-notes/whats-new-3.rst

@@ -337,7 +337,7 @@ parameter.
 Middleware configuration constraints
 -------------------------------------
 
-:class:`~litestar.middleware.ASGIMiddleware`\ s can now express constraints for how
+:class:`~litestar.middleware.base.ASGIMiddleware`\ s can now express constraints for how
 they are applied in the middleware stack, which are then validated on application
 startup.
 

docs/usage/middleware/creating-middleware.rst

@@ -25,7 +25,7 @@ Extending ``ASGIMiddleware``
 ----------------------------
 
 While using functions is a perfectly viable approach, the recommended way to handle this
-is by using the :class:`~litestar.middleware.ASGIMiddleware` abstract base class, which
+is by using the :class:`~litestar.middleware.base.ASGIMiddleware` abstract base class, which
 also includes functionality to dynamically skip the middleware based on ASGI
 ``scope["type"]``, handler ``opt`` keys or path patterns and a simple way to pass
 configuration to middlewares; It does not implement an ``__init__`` method, so
@@ -64,7 +64,7 @@ keep track of all these implicit couplings and dependencies, or downright imposs
 the middleware is implemented in a separate package and has no knowledge about how it is
 being applied.
 
-To help with this, :class:`~litestar.middleware.ASGIMiddleware` allows to specify a set
+To help with this, :class:`~litestar.middleware.base.ASGIMiddleware` allows to specify a set
 of :class:`~litestar.middleware.constraints.MiddlewareConstraints` - Once configured,
 these will be validated on application startup.
 
@@ -135,7 +135,7 @@ be the *last* middleware on the *last* layer (i.e. the route handler).
 Migrating from ``MiddlewareProtocol`` / ``AbstractMiddleware``
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
-:class:`~litestar.middleware.ASGIMiddleware` was introduced in Litestar 2.15. If you've
+:class:`~litestar.middleware.base.ASGIMiddleware` was introduced in Litestar 2.15. If you've
 been using ``MiddlewareProtocol`` / ``AbstractMiddleware`` to implement your middlewares
 before, there's a simple migration path to using ``ASGIMiddleware``.