Policy checks are skipped when looking up a share-type
by name. This causes share creation attempts that specify
a valid share-type to pass the early API check on share type
even if the share type named is private and not shared with
the user's project. The share creation fails later, but after
the database record for the share is created. Although the
operation fails with an ERROR, the share is stuck in CREATING
state.
Fix this issue by checking the user's project in the database
API just as we do for share type lookups by uuid.
Closes-bug: #1885956
Change-Id: If5fe32c155fe0861b3ed86b862335e062796056b
(cherry picked from commit f877deed51)
(cherry picked from commit e02cc6d6bc)
(cherry picked from commit 2f2ed258f7)
(cherry picked from commit 644cdf4e4f)
(cherry picked from commit 11971a94d3)
9b1b3957b9