Release v3.3.0 · mathieucarbou/ESPAsyncWebServer

Breaking Changes

This PR brings a lot of new feature and bug fixes:

Fixed method overloading for ESP8266
Added support for request attributes
Added support for middleware (aka Expressif Middleware): they can be added at server level (apply globally) or at handler level. They can act on the request and response and also decide if the processing continues or not (see examples)
Added support to replace a response with another one (e.g. a middleware could discard a response sent by a handler to create a new one)

Potential breaking changes:

Removed the "interesting headers" concept: all headers are now parsed. If you need to filter them out to only keep sone, you can use a middleware for that (see the examples)
Do not use setAuthentication() => use a middleware instead!
Do not use AsyncEventSource.authorizeConnect(...) => use a middleware instead!
Authentication is not checked anymore in the body / upload handlers (ArUploadHandlerFunction and ArBodyHandlerFunction) because these handlers are called once or more during the request parsing phase and the middleware chain cannot be called at this time and cannot be called also several time. It will be called during the handleRequest at the end. If you need to verify some auth in these callbacks, just create a middleware and call the method AuthenticationMiddleware.allowed(request)

Fix minor typos by @DRSDavidSoft in #96
(feat) Add support for request attributes by @mathieucarbou in #100
(perf) Remove "interesting headers" to fasten request processing (replaced with removeHeadersExcept) by @mathieucarbou in #101
Support for replacing a response by a new one by @mathieucarbou in #103
Fix method overload issue with ESP8266. ESP8266 has to use send_P() and beginResponse_p() variants by @mathieucarbou in #104
Add support for Middleware by @mathieucarbou in #98

Full Changelog: v3.2.4...v3.3.0