User with 'admin' role in secret/container project should have access even
when project-access is marked False (private). So modified policy rule and
adjusted unit test as earlier tested were generating error for 'admin' user.
Also fixed access issue related to user who initially created the secret or
container. In project access False case, that user can access secret or container
as long as that user token has 'creator' role in secret/container project.
Change-Id: I8ec1c29e0200c8af1706fdd474f4d96a10cf6449
Closes-bug: #1468904
Arun Kant
55c03ec22e