ProjectPolicy can require active SAML SSO session for web access

What does this MR do?

Builds on https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10034 by also restricting access to project resources

Why

Organizations want to guarantee that SSO was used rather than a password. The previous MR does most of the work and prevents access to group resources but many things in GitLab are nested under a project instead.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Performance and testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team