LPS-32912 At this moment, we must do this extra check in order to be sure that the servlet is only destroyed when the module framework is enabled. In the future this check will not be needed because the module framework will be available at any time
Test Fixes - portlet/messageboards
LPS-32901 "test-sample-sql" failed by LPS-32738
LPS-32719 Rename variables and constants to make more clear that they refer to the global scope
LPS-32719 Change scopeGroupId for siteGroupId
They will always be the same in this context, but the latter is the one that is correct from a semantic perspective.
LPS-32719 Extract logic to method without changing any behavior
LPS-32719 Move method to the proper class
LPS-32719 Support export/import of scope settings from one site to another respecting permissions
LPS-32719 If a page scope referenced from Asset Publisher does not exist it should be created

 This is now necessary because during import we are checking that the scopes selected in Asset Publisher are valid, so the group must be created at that point. This was already being done for the scope configuration of other portlets in PortletImporter.setPortletScope() so I just applied the same code. For the userId the most appropriate one in this case is the user doing the import.
LPS-32719 Add test to check for proper removing of invalid scope ids on import
LPS-32719 Fix invalid scope prefix in existing tests

This was not breaking previously because from the perspective of the test that prefix is not important. But now that the import logic interprets it to do a sanity check it must be correct.
LPS-32719 Use constants to avoid the same problem again
LPS-32719 Minor source formatting