Extract noauth context from ContextMiddleware

[Brian Waldon]

glance.common.context.ContextMiddleware handles coalescing keystone middleware headers into request context attributes. It also handles the situation where no upstream keystone middleware is deployed. These two things are completely opposite of one another and it makes more sense to have them be two separate middlewares. No reasonable environment will need both.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/7002

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/7002
Committed: http://github.com/openstack/glance/commit/eb4aaa97bd1e1c7e541a0ad109fb23dfee0f9c9d
Submitter: Jenkins
Branch: master

commit eb4aaa97bd1e1c7e541a0ad109fb23dfee0f9c9d
Author: Brian Waldon <email address hidden>
Date: Tue May 1 15:41:06 2012 -0700

    Split noauth context middleware into new class

    Use UnauthenticatedContextMiddleware in the case that you want to deploy
    without an auth service. ContextMiddleware is now solely for authenticated
    requests.

    * Rewrite ownership tests for adding/updating images through the v1 API
    * Fixes bug 992859

    Change-Id: I608671aac8300c9195769542708708afda991e04