Explicitly require the ComplianceManagement::ComplianceFramework dependency

What does this MR do?

Since we already have ComplianceFramework module defined in it's own file, if that file is not loaded into memory by autoload and if the other files within the namespace of ComplianceFramework are loaded into memory, accessing the attributes of that constant would raise error because autoload won't load that file since the module is already defined somewhere else.

To prevent this issue, we decided to explicitly load the ComplianceManagement::ComplianceFramework dependency in dependent files.

This is what's happening on my local environment right now.

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