Rework ProjectSecuritySetting with test table

The following discussion from !49167 (merged) should be addressed:

• @splattael started a discussion: (+1 comment)

  Non-blocking suggestion What do you think of using RSpec::Parameterized::TableSyntax to check all possible combinations to make the specs a bit easier on the eyes? 🤔 🤓

  (untested)

    where(:license, :feature_flag, :auto_fix_container_scanning, :auto_fix_dependency_scanning, :auto_fix_sast, :auto_fix_enabled?)
       true  | true  | true  | true  | true  | true 
       false | true  | true  | true  | true  | false
       true  | false | true  | true  | true  | false
       ...
       true  | true  | false | false | true  | true
       true  | true  | false | false | false | false

  WDYT?