Change default state for policy scope in security polices

What does this MR do and why?

This MR changed default state for policy scope

Policy scope for projects and group policies has default state as all projects in group instead of compliance frameworks

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Description	UI

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Enable Feature Flag

Feature.enable(:security_policies_policy_scope)

Feature.enable(:security_policies_policy_scope_project)

1. Go to Settings -> General
2. Toggle the Permissions and group features section
3. Enable Security policy scope
4. Go to Project
5. Secure -> Policies -> New Policy -> result or execution policy
6. Make sure you see UI for regular project under policy scope section (see in table)
7. Go to any other group or project
8. Secure -> Policies -> Edit policy project
9. Link project from step 3 to at least two other items (groups or projects)
10. Go back to project from step 3 and make sure you see UI SPP project with multiple linked projects (see in table)
11. Make sure default state for new policies is all projects in group
12. Go to a group
13. Secure -> Policies -> New Policy -> result or execution policy
14. Make sure default state for new policies is all projects in group

Related to #432513 (closed)