Enable profile "cloud" by default

[kwin]

Document disabling cloud profile
Fix GH actions build

This closes #3201

[kwin]

@royteeuwen Can you have a look at the PR?

[royteeuwen]

LGTM!

[kwin]

For some weird reason the build order is wrong:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for ACS AEM Commons - Reactor Project 6.3.1-SNAPSHOT:
[INFO] 
[INFO] ACS AEM Commons - Reactor Project .................. SUCCESS [  0.220 s]
[INFO] ACS AEM Commons Bundle ............................. SUCCESS [ 14.504 s]
[INFO] ACS AEM Commons Oakpal Checks ...................... SUCCESS [  1.347 s]
[INFO] ACS AEM Commons UI.Apps Package .................... SUCCESS [  4.820 s]
[INFO] ACS AEM Commons UI.Content Package ................. SUCCESS [  0.220 s]
[INFO] ACS AEM Commons Package ............................ SUCCESS [  0.775 s]
[INFO] ACS AEM Commons Bundle - Core Cloud Fragment ....... SUCCESS [  0.242 s]
[INFO] ------------------------------------------------------------------------

That is despite the fact hat ACS AEM Commons Package depends on the Core Cloud Fragment (in the profile cloud) and therefore must be built afterwards.

[kwin]

I created https://issues.apache.org/jira/browse/MNG-7926 for the ordering issue.

[kwin]

Actually it was just a misunderstanding from my side, the activeByDefault does no activate all profiles with the same id. This activation needs to be part of each (same named) profile, as profiles are not inherited. After activating all profiles cloud by default it works as expected.

[davidjgonzalez]

@kwin should this PR's build work? Or will this only work once we merge to main?

[kwin]

Only once we merge, GHA updates are never active from branches/forks due to security concerns.