refactor: asgimiddleware everywhere if possible

[euri10]

WIP

The middlewares are currently mostly based on either MiddlewareProtocol, AbstractMiddleware or AbstractAuthenticationMiddleware .

Their usage is spread around a few places:

1. using some kwags on the Litestar object, for instance: Litestar(allowed_hosts=allowed_hosts_config)
2. using the app_init kwargs on the Litestar object like in Litestar(on_app_init=[jwt_auth.on_app_init])
3. using a plugin through the plugins kwarg on the Litestar object.
4. using the middleware kwarg on the Litestar object trough the middleware property of the config, like for instance Litestar(middleware=[LoggingMiddlewareConfig().middleware]))
5. Using the handler decorator via middleware like in @get("/", middleware=[jwt_auth.middleware])

The idea of this PR is to:

1. switch them all to the shiny ASGIMiddleware (and BaseAuthenticationMiddleware which subclasses it)
2. allow their usage through either point 3-4-5 above

I think a logical subsequent step would be to remove entirely point 1 and 2 from the Litestar object, but that may go too far idk.

Current state:

Class	Parent Class	Usage
CSRFMiddleware	MiddlewareProtocol	1 > csrf_config
OpenTelemetryInstrumentationMiddleware	AbstractMiddleware	3 and 4
CORSMiddleware	AbstractMiddleware	1 > cors_config
AllowedHostsMiddleware	AbstractMiddleware	1 > allowed_hosts
CompressionMiddleware	AbstractMiddleware	1 > compression_config
LoggingMiddleware	AbstractMiddleware	4
RateLimitMiddleware	AbstractMiddleware	4
ResponseCacheMiddleware	AbstractMiddleware	1 > response_cache_config and 4
SessionMiddleware	AbstractMiddleware, Generic[BaseSessionBackendT]	4
PrometheusMiddleware	AbstractMiddleware	4
JWTAuthenticationMiddleware	AbstractAuthenticationMiddleware	2 and 5
SessionAuthMiddleware	AbstractAuthenticationMiddleware	4

Also, xxxMiddleware is often tied to xxxConfig, but there are some inconsistencies I didn't touch like for instance:
LoggingMiddlewareConfig is in litestar/middleware/logging.py along with the LoggingMiddleware

BUT for others there is a litestar/config folder that contains the CSRFConfig for instance ie config and middleware are seperated,
I can totally understand the split but since now xxxConfig is just a config for xxxMiddleware then I'd feel it would be better all are on the same middleware folder in their respective middleware

[provinzkraut]

Okay, I went through everything and it's looking quite good so far!

[euri10]

kept this now I remember to "showcase" the plugin is the same essentially as stacking the middlewares, now should you change their order and you're f**,

[provinzkraut]

Could we move the deprecation warnings to Litestar.__init__? Feels a bit odd in here

[provinzkraut]

Although on second thought, maybe it's okay to have them here, where they're actually being used

[euri10]

I tried to base my hotreload plugin of this branch and I get:

    try:
        import opentelemetry  # noqa: F401
    except ImportError as e:
>       raise MissingDependencyException("opentelemetry") from e
E       litestar.exceptions.base_exceptions.MissingDependencyException: Package 'opentelemetry' is not installed but required. You can install it by running 'pip install litestar[opentelemetry]' to install litestar with the required extra or 'pip install opentelemetry' to install the package separately

so I start to think the private _patch_opentelemetry_middleware is designed to handle the case where opentelemetry isnt installed ?

[github-actions]

Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/4055