One of the advantages of protection tests is to make sure glance is
doing the right thing with oslo.policy. This commit increase the
oslo.policy debug logging so we can more easily see what's going on in
logs.

Change-Id: I9515dff85f8d00c657ca7053b21202d530098ccf

This commit builds on
https://review.opendev.org/c/openstack/glance-tempest-plugin/+/773568 by
adding explicit tempest protection tests for sharing images between
projects, image deactivation, and reactivation.

Depends-On: https://review.opendev.org/c/openstack/tempest/+/778753

Change-Id: Ia57440962140fe9f8d47c29b1b49dfbe9f846149

This commit lays down some basic protection tests so that we can start
testing the secure RBAC changes proposed to glance. It also adds a
.zuul.yaml so that we can run the tests as check and gate jobs.

Change-Id: I35d6b546da260f3f6b5c427a17ee3509cdc41277

This must have been left over copy/pasta from when the tempest plumbing
was laid down during the community goal.

Change-Id: Id4e788395483187e15f000b11b1ad612b5c5093e

We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removed specific doc requirements from test-requirements.txt.

The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.

This project meet the conditions leading to the bug.

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36

Change-Id: If9...