Enable compliance pipeline configuration by default

What does this MR do?

Adds documentation changes for compliance pipeline configuration and enables the flag by default.

The reason for enabling the flag by default as opposed to removing it is because ff_evaluate_group_level_compliance_pipeline feature flag depends on Compliance frameworks feature flag, that is enabled by default. By enabling by default, we have an option to disable this feature flag, in case the compliance framework ff had to be turned off.

Mentions &3156 (closed) and #300324 (closed)

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability 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
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

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