Replace trivial instances of tenant for project

This patch replaces the trivial instances were the word tenant is used.
No model is touched yet.

Partially implements: blueprint replace-concept-of-tenants-for-projects

Change-Id: Id21a34d2c414e0497a943ace970584369bd1d83f
Remove redundant else, none returned by default

Change-Id: I5ad90fab3105ce07d979dedde2b165453d80c0ec
Merge "Remove redundant else, none returned by default"
Cleaning up a couple nits in the Symantec plugin

Change-Id: I1afa289db566103de90e57cbb9dd6a370be8f021
Excluding alembic migrations from coverage

Currently we cannot tests the migrations within our unit test setup. We
should look into alternative ways of testing migrations and their
coverage.

Change-Id: I5fbc4957a7ed1e0924bce562530adbe5fd2d966b
Merge "Cleaning up a couple nits in the Symantec plugin"
Merge "Excluding alembic migrations from coverage"
Merge "Replace trivial instances of tenant for project"
Added smoke tests for containers

Added all smoke tests and supporting classes for containers.

Change-Id: I46ff758d262c3188d476672f7d5dd9e7fad5ad73
Fixing remaining hacking violations

The cleans up all remaining hacking violations and updates the test-
requirements to the latest approved version of hacking so we don't
regress on violations again.

Deleted several duplicated test cases (so I didn't have to fix the
hacking violations in them):

* test_secret_create_nones_blank_name_and_valid_content_type
* test_secret_get_defaults_none_as_bit_length
* test_secret_create_defaults_null_name

Change-Id: I21c7af4160c62222af0e54b947e301bc900250e6
Use "key-manager" for service type

Use "key-manager" as the service type for the Keystone catalog, as it is
a better description of the service, and is more in-line with with the
official program name "Key Management Service".

Change-Id: I1c76dc8e3817b790c9a082c50684af85a1107166
Merge "Use "key-manager" for service type"
Fix communication of secret_type info

Change-Id: Ie7d70463e144dfd0c862dc43d7a32e8e8e0d35ea
Added test to check that an expired secret cannot be retrieved

Added a single test that creates and expires a secret.
The test then checks that secret can no longer be retrieved.

Change-Id: Iaf2a250f4f554509cdef1adf82ca1682a0047e0b
Updated from global requirements

Change-Id: I802b75cd315cd45835efc334a9bce2695a08cdc9
Updated from global requirements

Change-Id: I3ce9b48763b295c2e3cca2621d0f7e6fb785d38d
Use canonical name for coverage job

Use "cover" for the coverage tox environment.  Also removed the unused
tox environment previously using "cover" as the name.

Change-Id: I48be7f673ad701c3b506548c1c30e51a076054b0
Merge "Use canonical name for coverage job"
Merge "Added test to check that an expired secret cannot be retrieved"
Updated from global requirements

Change-Id: I4ebbbc4237baaba099b65579c33be33edbe1557b