Improve feature toggle text and organization

Current state

Desired state

1. Updated description
   1. Include link to docs
   2. Suggested top description: These features are being developed and might be unstable and are are subject to the Testing Terms of Use.
   3. Leave off What do Experiment and Beta mean? -- it will be listed immediately after in the "Experiment and Beta features" area and I think we'll soon have a more organized section soon for all toggles, which may allow us to avoid repeating these points.
2. Remove double use of "experiment" and a short description
   1. "Security policy pipeline execution action" [Experiment]
      1. Create and enforce custom CI jobs and scripts using this new policy action. Learn more.
   2. "Security policy scope" [Experiment]
      1. Granularly scope each policy you create to projects containing a compliance framework label, or a list of projects. Learn more.
3. Organize toggles under one testing agreement section, as discussed here. Use title Security Policy Management.

4. Move the experiment toggle location to sit next to other experiments (e.g. Code Suggestions).
   1. List our section under Code Suggestions and above "Experiment and Beta features"