Add a branch to test a 'profile' project type

I have created a d10-profile branch and now we can expand the composer.json to load some modules and themes

Using MR10 with the current Gitlab Template, the pipeline shows that:

• /modules/contrib contains the 3rd-party modules (correct)
• /modules/custom contains this profile (wrong, should be profiles/custom)
• /themes contains the 3rd-party themes (wrong, should be themes/contrib)

Here's a downstream pipeline from MR334 using this MR10 branch

• /modules/contrib still contains the correct 3rd-party modules
• /modules/custom no longer exists (correct)
• /profiles/custom is created and contains this project (correct)
• /themes/contrib is now created and contains the 3rd-party modules (correct)

These additions show that the fixes in MR344 are working as required.

Is there anything else to add here, before I merge this MR?

The changes look good. It's a great way to test profiles/themes/modules!

Thank you. Merged.

Automatically closed - issue fixed for 2 weeks with no activity.