feat: move litestar.contrib.prometheus to litestar.plugins.prometheus

[cofin]

Description

feat: deprecate litestar.contrib.prometheus in favor of the new location of litestar.plugins.prometheus

Closes

[codecov]

Codecov Report

Attention: Patch coverage is 99.45355% with 1 line in your changes missing coverage. Please review.

Project coverage is 98.41%. Comparing base (1b9d1c8) to head (d43293d).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
litestar/plugins/prometheus/middleware.py	98.75%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3863   +/-   ##
=======================================
  Coverage   98.41%   98.41%           
=======================================
  Files         339      343    +4     
  Lines       15416    15456   +40     
  Branches     1702     1702           
=======================================
+ Hits        15171    15211   +40     
  Misses        115      115           
  Partials      130      130           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[JacobCoffee]

sorry maybe a dumb q - what is the benefit here of moving from contrib to plugins aside from renaming it?

also i feel like this one is a good candidate to move outside of the stdlib into its own package and then we can assign it as an extra

[cofin]

sorry maybe a dumb q - what is the benefit here of moving from contrib to plugins aside from renaming it?

also i feel like this one is a good candidate to move outside of the stdlib into its own package and then we can assign it as an extra

The goal is to get any non-essential core code into a plugin style structure. Right now, we have both litestar.plugins and litestar.contrib and it's contributing to code sprawl and additional maintenance overhead.

Re: the move to an external library I also agree. In fact, I think most (maybe all) of the plugins can ultimately be treated that way. We can do that in steps though.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

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