rep:policy node in /apps not created by ui.apps package after split

[adamcin]

Required Information

• AEM Version, including Service Packs, Cumulative Fix Packs, etc: n/a
• ACS AEM Commons Version: 4.3.2
• Reproducible on Latest? yes

Expected Behavior

/apps/rep:policy should be created by ui.apps during oakpal scan to establish policies for acs-aem-commons system users.

Actual Behavior

from @ataimussova : There is an issue due to the split as rep:policy for apps are not being applied. The reason is that rep:policy is in ui.apps package and users are in ui.content. Due to the order of ui.apps being installed prior to ui.content, as a result system users have no access to /apps. It happens if you have no previous version of ACS AEM Commons installed because there are no ACS AEM Commons system users. Could you please fix?

Steps to Reproduce

I added a simple inline check to verify this situation with oakpal:

<check>
   <name>verify-acls</name>
   <inlineScript>
      function afterExtract(packageId, session) {
         if (!session.itemExists("/apps/rep:policy")) {
            oakpal.majorViolation("expected /apps/rep:policy node to be created", packageId);
         }
      }
   </inlineScript>
</check>

This is the result:

[INFO] --- oakpal-maven-plugin:1.4.2:verify (oakpal-verify) @ acs-aem-commons-ui.apps ---
[INFO] OakPAL Check Reports
[INFO]   verify-acls
[ERROR]    +- <MAJOR> expected /apps/rep:policy node to be created [acs-aem-commons-ui.apps-4.3.3-SNAPSHOT.zip]
[INFO]   verify-acls
[ERROR]    +- <MAJOR> expected /apps/rep:policy node to be created [acs-aem-commons-ui.apps-4.3.3-SNAPSHOT.zip]
[INFO]   verify-acls
[ERROR]    +- <MAJOR> expected /apps/rep:policy node to be created [acs-aem-commons-ui.apps-4.3.3-SNAPSHOT.zip]
[INFO]   verify-acls
[ERROR]    +- <MAJOR> expected /apps/rep:policy node to be created [acs-aem-commons-ui.apps-4.3.3-SNAPSHOT.zip]
[ERROR] ** Violations were reported at or above severity: MAJOR **