Preparation work to allow the allocation of the HTTP
request context for use in the ProjectQoSFilter.
Having separate filters for setting the current context
and cleaning it up, allows other filters, like ProjectQoSFilter,
to access the current user without having necessarily to
have its context cleaned up.
The first attempt to have ProjectQoSFilter with a context
has failed because the cleanup was done on the upstream
filter, causing a double invocation and thus an exception.
By having the context set *before* the ProjectQoSFilter and
then cleaned up *after* the filter, allows to have the current
user injected and still doing the cleanup only once the filter
has correctly finished its processing.
Bug: Issue 12070
Change-Id: I7fbda3d787f54ef6af6d6ae75c28d4d73ba197fb