-
* There is already a fix in place for #421528 via !129742 * This is a refactor that ensures we proactively *prevent* this ability if security_and_compliance_disabled is on for a project. Now, we don't need to worry about always checking `~security_and_access_disabled` before enabling `access_security_and_compliance` because it is prevented and with our policy framework (Declarative Policy), one prevention is all that is needed to block the ability. * Having these checks be flatter is more efficient for Declarative Policy: https://gitlab.com/gitlab-org/ruby/gems/declarative-policy/-/blob/main/doc/optimization.md?ref_type=heads#flat-is-better-than-nested