In previous Zope versions string exceptions were used and all exceptions
re-raised. This doesn't work with each kind of exception, but we can still do
it with Unauthorized exceptions. This way the special handling for Unauthorized
exceptions works again, HTTPResponse._unauthorized is called again. This is now
done after rendering to make sure we don't break logging and custom views.

Such cookies violate RFC 2965 / 2616.

Fixes LP #563229.

It is very unlikely that v is a tuple and 'hasattr(sys, 'exc_info')' is always true.

- *Broken* because re-raising doesn't work with more than one required argument. "Needs to be able to take more than two arguments" was a wrong assumption.
- *Useless* because the code below never tries to re-raise rendered errors. That's the reason why the wrong check never caused trouble.

'handle_errors' is *always* true at this point because otherwise the error would have been re-raised in line 270.
Removed the raise statement because it was unreachable.

o Use the lexicon's pipeline (e.g., case flattening, stop word removal, etc.)

o Forward-port from 2.12 branch.

o Use the lexicon's pipeline (e.g., case flattening, stop word removal, etc.).