feat: plugin support

[bjohansebas]

Summary

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

If relevant, what needs to be documented once your changes are merged or what have you already documented?

[codecov]

Codecov Report

❌ Patch coverage is 94.64286% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.10%. Comparing base (93c191a) to head (3e742d1).
⚠️ Report is 1 commits behind head on next.

Files with missing lines	Patch %	Lines
lib/Server.js	94.64%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #5650      +/-   ##
==========================================
+ Coverage   83.73%   84.10%   +0.36%     
==========================================
  Files          11       11              
  Lines        1943     1988      +45     
  Branches      720      730      +10     
==========================================
+ Hits         1627     1672      +45     
  Misses        283      283              
  Partials       33       33              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[alexander-akait]

We should start it in webpack-dev-middleware, currently webpack-dev-middleware uses console.log to output stats, it means we will spam logs, we need an options or another function wrapper - require("webpack-dev-middleware").plugin(options)

[bjohansebas]

These changes should work without requiring any changes to webpack-cli yet. Once this is merged, we can work on a patch for webpack-cli to use the plugin support, but it is independent of changes to webpack-cli.

[bjohansebas]

cc: @alexander-akait friendly ping for feedback