Special request attributes might not be set with multiple wrappers

When multiple layers of the http wrappers are used with custom wrappers in between, special request attributes might not be set properly. This includes attributes for error handling, include/forward request dispatching.
For example:

• the original request is a jakarta.servlet request
• this is wrapper in a javax.servlet request
• which is then wrapper by a javax.servlet request wrapper
• which is then wrapped by jakarta.servlet request wrapper
  If now a special attribute is set on the latest request object, the implementation of setAttribute causes it to be set first, but then calls removeAttribute - which in turn will wipe out the value