Add ability to delete compliance framework via graphql

What does this MR do?

• Builds on recently created ComplianceManagement::Frameworks::DestroyService
• Adds a new GraphQL mutation: destroyComplianceFramework
• Allows destruction by group/namespace owners of compliance frameworks.
• Behind feature flag - ff_custom_compliance_frameworks created in !47779 (merged).

## Example

mutation {
  destroyComplianceFramework(input: { id: "gid://gitlab/ComplianceManagement::Framework/19" }) {
    errors
  }
}

Successful Response

{
  "data": {
    "destroyComplianceFramework": {
      "errors": []
    }
  }
}

Unsuccessful response

• Feature (custom_compliance_frameworks) is not licensed (Ultimate) OR
• Feature flag (ff_custom_compliance_frameworks) is not enabled OR
• Currently authenticated user is not allowed to destroy the framework.

{
  "data": {
    "destroyComplianceFramework": {
      "errors": ["Not permitted to destroy framework"]
    }
  }
}

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• 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

Related to #255340 (closed)